HomeWordPress vulnerabilitiesPage and Post Restriction
Page and Post Restriction vulnerabilities
Page and Post Restriction has 2 known vulnerabilities in this database. The most recent published record is dated 5 Aug 2026.
- Known vulnerabilities
- 2
- Active installs
- 2,000+
- Latest version
- 1.6.0
- Last updated
- 29 Sep 2026
- Most recent
- 5 Aug 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Sensitive data exposure CVE-2026-12000 | High 7.5 | Up to 1.4.0 | Fixed in a later version (latest 1.6.0) | 5 Aug 2026 |
| Sensitive data exposure CVE-2024-11297 | Medium 5.3 | Before 1.3.7 | Fixed in 1.3.7 | 20 Dec 2024 |
Read the published descriptions
- CVE-2026-12000, 5 Aug 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 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(). CVE record
- CVE-2024-11297, 20 Dec 2024
- The Page Restriction WordPress (WP) - Protect WP Pages/Post plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.3.6 via the WordPress core search feature. This makes it possible for unauthenticated attackers to extract sensitive data from posts that have been restricted to higher-level roles such as administrator. CVE record
What to do if you run Page and Post Restriction
If you run Page and Post Restriction, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Page and Post Restriction vulnerabilities
Free. We email you when a new vulnerability is published for Page and Post Restriction, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.