CVE-2026-12000: Page and Post Restriction <= 1.4.1 - Unauthenticated Missing Authorization to Sensitive Information Exposure via REST API
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 — paprrestrictpagepostrestapi() and the theposts filter registered by paprfilterposts() — sourcing their restricted-ID list exclusively from paprgetrestrictedpostsid(), which only reads the per-page metabox options paprallowedredirectforpages and paprallowedredirectforposts and never consults the two global toggles papraccessforonlyloggedin and papraccessforonlyloggedinposts 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 paprrestrictloggedinusers().
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
WordPress Page and Post Restriction pluginto a version that resolves this vulnerability.Fixed in 1.4.1