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().
Published: 2026-08-05
Score: 7.5 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The Page and Post Restriction plugin for WordPress is vulnerable to sensitive information exposure in versions up to and including 1.4.1. Unauthenticated attackers can retrieve the full rendered content of every published page and post through the 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 bypasses the intended access restrictions designed to make pages or posts private, exposing potentially confidential site content without authentication. The weakness is a missing authorization check, identified as CWE‑862.

Affected Systems

WordPress sites that have the Page and Post Restriction plugin by cyberlord92 installed, with any version up to 1.4.1. Sites that have enabled the global toggles to make all Pages or Posts Private are especially at risk, as the plugin ignores these settings when guarding REST API calls.

Risk and Exploitability

The CVSS score of 7.5 indicates a high severity vulnerability. Exploitation requires no credentials; the attacker simply sends a HTTP GET request to the exposed REST endpoints over the public web, making the attack highly feasible. The EPSS score is not available, but the wide usage of WordPress and the common deployment of this plugin suggest a realistic attack probability. The vulnerability is not listed in the CISA KEV catalog at present, but because it can reveal all page and post content, it poses a substantial confidentiality risk if the site hosts valuable or proprietary material.

Generated by OpenCVE AI on August 5, 2026 at 08:26 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the Page and Post Restriction plugin to version 1.4.2 or later to fix the missing authorization checks.
  • If an immediate upgrade is not possible, block or disable the REST API routes for pages and posts (for example, using a security plugin or server configuration such as restricting /wp-json/wp/v2/pages and /wp-json/wp/v2/posts to authenticated users only).
  • Confirm that the global "Make all Pages Private" and "Make all Posts Private" options are enabled and that no custom code or additional plugins override the plugin’s default restriction behavior.

Generated by OpenCVE AI on August 5, 2026 at 08:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 05 Aug 2026 07:30:00 +0000

Type Values Removed Values Added
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().
Title Page and Post Restriction <= 1.4.1 - Unauthenticated Missing Authorization to Sensitive Information Exposure via REST API
Weaknesses CWE-862
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-08-05T06:38:02.526Z

Reserved: 2026-06-11T16:18:11.549Z

Link: CVE-2026-12000

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-05T08:30:04Z

Weaknesses