Reported vulnerability

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

Q: Which versions of Page and Post Restriction are affected?

Wordfence lists these affected versions: Start version unspecified, through 1.4.1. Use the version checker above to compare your installed release with this report.

Q: Is a fix available for Page and Post Restriction?

Wordfence reports a fix for this issue in Page and Post Restriction. It lists these fixed versions: 1.4.2. Back up your website and test the recommended update before applying it to your live site.

Q: Where can I find my installed plugin version?

In WordPress, open Plugins > Installed Plugins and find the version shown beneath the plugin name.

Published 4 Aug 2026

Updated 5 Aug 2026

CVE-2026-12000

Compare your installed software with the affected versions below. Follow the source’s remediation guidance and test an available update after taking a backup. A database entry describes a reported issue; it does not establish whether a particular website has been compromised.

Does this affect my version?

Check your installed version against this advisory. This compares the report’s version ranges and does not scan your website.

Wordfence advisory

high · CVSS 7.5

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/, /wp-json/wp/v2/posts, and /wp-json/wp/v2/posts/. 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().

Severity vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Page and Post Restriction

Software: plugin · page-and-post-restriction
Affected versions: Start version unspecified, through 1.4.1
Fix availability: Fix available
Fixed versions: 1.4.2

Recommended action

Update to version 1.4.2, or a newer patched version

Further references (1)

wordfence.com/threat-intel/vulnerabilities/id/f01302aa-00ef-440a-9c37-4fde6bb4bb4d?source=api-prod

Data sources and licences

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

Read licence terms

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

Read licence terms

Source: Wordfence

Need help fixing this issue?

Get help checking your site, applying an available update and resolving any problems after updating.

Get help with this issue

Questions about this vulnerability

Which versions of Page and Post Restriction are affected?

Wordfence lists these affected versions: Start version unspecified, through 1.4.1. Use the version checker above to compare your installed release with this report.

Is a fix available for Page and Post Restriction?

Wordfence reports a fix for this issue in Page and Post Restriction. It lists these fixed versions: 1.4.2. Back up your website and test the recommended update before applying it to your live site.

Where can I find my installed plugin version?

In WordPress, open Plugins > Installed Plugins and find the version shown beneath the plugin name.

Does an affected version mean my website has been hacked?

An affected version means the installed release matches a vulnerability described in this report. It does not show whether anyone has exploited it on your website. The checker compares version numbers with stored reports; it does not inspect your website.

These reports cover at least one of the same plugins, themes or WordPress core. Check each report’s affected versions separately.

Back to vulnerability database