VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

Page Restriction WordPress (WP) – Protect WP Pages/Post <= 1.3.4 — Protection Mechanism Bypass

CVE-2024-0681Published · Updated

Action summary

Affected: ≤1.3.4Update to 1.3.5 or newer

All remediation steps
Watch plugin
Severity
Medium5.3
CVSS
5.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:L Confidentiality
Low
I:N Integrity
None
A:N Availability
None
Weakness
CWE-693 Protection Mechanism Failure
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed
On this page8

Am I affected?

Page and Post Restriction page-and-post-restriction

  1. Affected≤ 1.3.4
  2. Patched in1.3.5

Update to 1.3.5 or newer.

You are affected if you run ≤ 1.3.4. Version 1.3.5 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Page and Post Restriction.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 1.3.5, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Page and Post Restriction to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Francesco Carlucci.

The Page Restriction WordPress (WP) – Protect WP Pages/Post plugin for WordPress is vulnerable to information disclosure in all versions up to, and including, 1.3.4. This is due to the plugin not properly restricting access to pages via the REST API when a page has been made private. This makes it possible for unauthenticated attackers to view protected pages. The vendor has decided that they will not implement REST API protection on posts and pages and the restrictions will only apply to the front-end of the site. The vendors solution was to add notices throughout the dashboard and recommends installing the WordPress REST API Authentication plugin for REST API coverage.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Page and Post Restriction

All 7
More vulnerabilities in Page and Post Restriction
SeverityVulnerabilityCVEPublished
Medium6.5Unauthenticated Authentication Bypass via REST API Nonce Bypass via Cookie Re-Authentication
≤1.6.1Update to 1.6.2
CVE-2026-118194
Medium5.3Missing Authorization
≤1.6.1Update to 1.6.2
CVE-2026-54852
Medium5.3Missing Authorization
≤1.6.0Update to 1.6.1
CVE-2026-114696
High7.5Unauthenticated Missing Authorization to Sensitive Information Exposure via REST API
≤1.4.1Update to 1.4.2
CVE-2026-12000
Medium5.3Unauthenticated Content Restriction Bypass to Sensitive Information Exposure
≤1.3.6Update to 1.3.7
CVE-2024-11297

Timeline

  1. CVE published

    Severity medium, CVSS 5.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?