Page Restrict
pagerestrict · plugin
Known security vulnerabilities for Page Restrict. Find out in seconds which version runs on your site with WP Lens.
2 known vulnerabilities
2 exploitable without logging in · latest Feb 28, 2024
Closed on wordpress.org
Removed from the directory on May 31, 2024 · reason: security issue. A closed component gets no more updates; installed copies keep running and their vulnerabilities stay open. Remove it or replace it with a maintained alternative.
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- High 8.8
CVE-2024-24702unauthenticated · needs a click≤ 2.5.5
WordPress Page Restrict Plugin <= 2.5.5 is vulnerable to Cross Site Request Forgery (CSRF)
- Medium 5.3
CVE-2024-0682unauthenticated≤ 2.5.5
Page Restrict <= 2.5.5 - Protection Mechanism Bypass
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).