Skip to content

CVE-2026-12000 Page and Post Restriction <= 1.4.1 - Unauthenticated Missing Authorization to Sensitive Information Exposure via REST API

HighCVSS 7.5 EPSS 0.69%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: yes · technical impact: partial
Technology
WordPress

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().

Upgrade path

2 packages: 2 fixed.

PackageAffectedFixed inStatus
cyberlord92 Page and Post Restriction <= 1.4.1 after 1.4.1 Fixed
wordpress page-and-post-restriction(WordPress) < 1.4.2 1.4.2 Fixed

Affected products

ProductAffected versionsFixed in
cyberlord92 Page and Post Restriction <= 1.4.1 No fix listed
wordpress page-and-post-restriction(WordPress) < 1.4.2 1.4.2

References