PT-2026-68014 · WordPress · Page/Post Restriction

·

CVE-2026-12000

·

Published

2026-08-05

·

Updated

2026-08-05

CVSS v3.1

7.5

High

VectorAV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Name of the Vulnerable Software and Affected Versions Page and Post Restriction versions prior to 1.4.1
Description Sensitive information exposure occurs 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/'. The issue stems from the REST guards papr restrict page post rest api() and the the posts filter registered by papr filter posts() relying solely on papr get restricted posts id(). This function only reads the per-page metabox options papr allowed redirect for pages and papr allowed redirect for posts, ignoring the global toggles papr access for only loggedin and papr access for only loggedin posts used to make all pages or posts private. Consequently, unauthenticated attackers can read the full rendered content of every published page and post, bypassing the security boundary enforced by papr restrict logged in users() on the frontend.
Recommendations Update the plugin to a version later than 1.4.0.

Fix

Missing Authorization

Found an issue in the description? Have something to add? Feel free to write us 👾

Weakness Enumeration

Related Identifiers

CVE-2026-12000

Affected Products

Page/Post Restriction