CVE-2026-12000 Missing authorization in Page and Post Restriction
Unauthenticated attackers can read private page and post content via REST API when global privacy toggles are enabled, bypassing frontend restrictions.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-12000?
CVE-2026-12000 is a high-severity missing authorization vulnerability in cyberlord92 Page and Post Restriction, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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().
Weakness: CWE-862
Which versions are affected by CVE-2026-12000?
How do I fix CVE-2026-12000?
No fix has been published for CVE-2026-12000 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-12000 being exploited?
There is no known exploitation of CVE-2026-12000 in the wild and no public exploit code.
Sources
Also known as GHSA-j2cm-38v7-pfcv.