CVE-2026-12000

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-05. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The Page and Post Restriction plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to and including 1.4.0 via the WordPress core REST endpoints /wp-json/wp/v2/pages, /wp-json/wp/v2/pages/, /wp-json/wp/v2/posts, and /wp-json/wp/v2/posts/. This is due to the plugin's REST guards — papr_restrict_page_post_rest_api() and the the_posts filter registered by papr_filter_posts() — sourcing their restricted-ID list exclusively from papr_get_restricted_posts_id(), which only reads the per-page metabox options papr_allowed_redirect_for_pages and papr_allowed_redirect_for_posts and never consults the two global toggles papr_access_for_only_loggedin and papr_access_for_only_loggedin_posts that the plugin's own UI describes as 'Make all Pages Private' / 'Make all Posts Private'. This makes it possible for unauthenticated attackers to read the full rendered content of every published page and post on sites configured with the documented global toggles, bypassing the security boundary enforced on the frontend by papr_restrict_logged_in_users().

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

August 5, 2026

Last Modified

August 12, 2026

References (10)

Vendor Advisories for CVE-2026-12000(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 28× in last 7d / 68× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 02:39 UTCEG score recompute
  2. 2026-08-21 02:39 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 14:20 UTCGHSA enrichment
  5. 2026-08-20 01:47 UTCEG score recompute
  6. 2026-08-20 01:47 UTCGHSA enrichment
  7. 2026-08-19 17:03 UTCEPSS rescore
  8. 2026-08-19 13:28 UTCGHSA enrichment
  9. 2026-08-19 01:09 UTCEG score recompute
  10. 2026-08-19 01:09 UTCGHSA enrichment
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-18 12:49 UTCGHSA enrichment
  13. 2026-08-18 00:16 UTCEG score recompute
  14. 2026-08-18 00:15 UTCGHSA enrichment
  15. 2026-08-17 11:52 UTCGHSA enrichment
  16. 2026-08-16 23:34 UTCEG score recompute
  17. 2026-08-16 23:34 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 11:16 UTCEG score recompute
  20. 2026-08-16 11:16 UTCGHSA enrichment
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 22:58 UTCGHSA enrichment
  23. 2026-08-15 10:40 UTCEG score recompute
  24. 2026-08-15 10:40 UTCGHSA enrichment
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 43 more
  1. 2026-08-14 22:21 UTCGHSA enrichment
  2. 2026-08-14 10:03 UTCEG score recompute
  3. 2026-08-14 10:03 UTCGHSA enrichment
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-13 21:44 UTCGHSA enrichment
  6. 2026-08-13 09:26 UTCGHSA enrichment
  7. 2026-08-12 21:07 UTCGHSA enrichment
  8. 2026-08-12 19:44 UTCEG score recompute
  9. 2026-08-12 19:44 UTCGHSA enrichment
  10. 2026-08-12 13:50 UTCEPSS rescore
  11. 2026-08-12 07:26 UTCGHSA enrichment
  12. 2026-08-11 19:07 UTCEG score recompute
  13. 2026-08-11 19:07 UTCGHSA enrichment
  14. 2026-08-11 13:42 UTCEPSS rescore
  15. 2026-08-11 06:49 UTCEG score recompute
  16. 2026-08-11 06:49 UTCGHSA enrichment
  17. 2026-08-10 23:59 UTCEPSS rescore
  18. 2026-08-10 18:31 UTCGHSA enrichment
  19. 2026-08-10 06:12 UTCGHSA enrichment
  20. 2026-08-09 17:54 UTCEG score recompute
  21. 2026-08-09 17:54 UTCGHSA enrichment
  22. 2026-08-09 13:46 UTCEPSS rescore
  23. 2026-08-09 05:36 UTCGHSA enrichment
  24. 2026-08-08 17:18 UTCEG score recompute
  25. 2026-08-08 17:18 UTCGHSA enrichment
  26. 2026-08-08 16:37 UTCEPSS rescore
  27. 2026-08-08 04:59 UTCGHSA enrichment
  28. 2026-08-07 16:41 UTCEG score recompute
  29. 2026-08-07 16:41 UTCGHSA enrichment
  30. 2026-08-07 04:22 UTCGHSA enrichment
  31. 2026-08-06 16:04 UTCEG score recompute
  32. 2026-08-06 16:04 UTCGHSA enrichment
  33. 2026-08-06 13:46 UTCEPSS rescore
  34. 2026-08-06 03:45 UTCEG score recompute
  35. 2026-08-06 03:45 UTCGHSA enrichment
  36. 2026-08-05 19:17 UTCEPSS rescore
  37. 2026-08-05 15:27 UTCEG score recompute
  38. 2026-08-05 15:27 UTCGHSA enrichment
  39. 2026-08-05 14:37 UTCEG score recompute
  40. 2026-08-05 14:37 UTCGHSA enrichment
  41. 2026-08-05 08:23 UTCEG score recompute
  42. 2026-08-05 07:23 UTCEG score recompute
  43. 2026-08-05 07:20 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-12000?
CVE-2026-12000 is a high vulnerability published on August 5, 2026. The Page and Post Restriction plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to and including 1.4.0 via the WordPress core REST endpoints /wp-json/wp/v2/pages, /wp-json/wp/v2/pages/<id>, /wp-json/wp/v2/posts, and /wp-json/wp/v2/posts/<id>. This is due to the…
When was CVE-2026-12000 disclosed?
CVE-2026-12000 was first published in the National Vulnerability Database on August 5, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12000 actively exploited?
CVE-2026-12000 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 51.0% of all scored CVEs.
What is the CVSS score of CVE-2026-12000?
CVE-2026-12000 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-12000?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12000, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-12000

Explore →

Is Your Infrastructure Affected by CVE-2026-12000?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs