WordPress plugin
Page Restrict security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the plugin or restrict access to the affected feature until the vendor ships a patch.
- Critical0
- High0
- Medium3
- Low0
All Page Restrict vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium5.3 | Protection Mechanism Bypass ≤2.5.5No patch available | CVE-2024-0682 | |
| Medium4.3 | Cross-Site Request Forgery via pr_admin_page ≤2.5.5No patch available | CVE-2024-24702 | |
| Medium6.5 | Stored Cross-Site Scripting <2.2.2Update to 2.2.2 | — |
- Medium5.3Protection Mechanism Bypass
≤2.5.5No patch available
- Medium4.3Cross-Site Request Forgery via pr_admin_page
≤2.5.5No patch available
- Medium6.5Stored Cross-Site Scripting
<2.2.2Update to 2.2.2
Page Restrict: common questions
Does Page Restrict have known vulnerabilities?
Yes. VulnCrest Radar lists 3 known vulnerabilities in Page Restrict: 3 medium. At least one is not fixed in the latest version.
How do I check which version of Page Restrict I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent Page Restrict vulnerability?
CVE-2024-0682, published Feb 27, 2024: Page Restrict <= 2.5.5 - Protection Mechanism Bypass. Severity: Medium (CVSS 5.3).
Is any Page Restrict vulnerability listed in CISA KEV?
No. None of the known Page Restrict vulnerabilities is currently listed in the CISA KEV catalog.