CVE-2026-12000 json
Page and Post Restriction <= 1.4.1 - Unauthenticated Missing Authorization to Sensitive Information Exposure via REST API
published 3mo ago modified 2mo ago also EUVD-2026-53188
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
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 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().
Is CVE-2026-12000 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 3mo ago
Exploit prediction
0.69% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- cyberlord92 Page and Post Restriction
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/f01302aa-00ef-440a-9c37-4fde6bb4bb4d?source=cve
- plugins.trac.wordpress.org /browser/page-and-post-restriction/tags/1.4.1/page-and-post-restriction.php#L69
- plugins.trac.wordpress.org /browser/page-and-post-restriction/tags/1.4.1/page-restriction-utility.php#L701
- plugins.trac.wordpress.org /browser/page-and-post-restriction/tags/1.4.1/page-and-post-restriction.php#L94
- plugins.trac.wordpress.org /browser/page-and-post-restriction/tags/1.4.1/page-and-post-restriction.php#L484
- plugins.trac.wordpress.org /browser/page-and-post-restriction/tags/1.4.0/page-and-post-restriction.php#L69
- plugins.trac.wordpress.org /browser/page-and-post-restriction/tags/1.4.0/page-restriction-utility.php#L701
- plugins.trac.wordpress.org /browser/page-and-post-restriction/tags/1.4.0/page-and-post-restriction.php#L94
- plugins.trac.wordpress.org /browser/page-and-post-restriction/tags/1.4.0/page-and-post-restriction.php#L484
- plugins.trac.wordpress.org /changeset?new=3578420%40page-and-post-restriction%2Ftags%2F1.4.2&old=3560846%40page-and-post-restriction%2Fta
Sources
- CVE List CVE-2026-12000
- NVD CVE-2026-12000
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.