PatchSiren cyber security CVE debrief
CVE-2025-8945 Wp Edit Password Protected CVE debrief
CVE-2025-8945 is a medium-severity vulnerability in the Wp Edit Password Protected WordPress plugin. The plugin's protection of page content can be bypassed using the REST API. This issue was publicly disclosed on September 2, 2026, and the CVE record was last modified on September 3, 2026. Defenders should assess exposure and prioritize verification and remediation efforts for WordPress installations using the Wp Edit Password Protected plugin, especially those allowing REST API access. The vulnerability allows bypassing page content protection, which could lead to unauthorized access to sensitive information. The CVE record and NVD entry provide limited information about the CVE
- Vendor
- Wp Edit Password Protected
- Product
- Wp Edit Password Protected
- CVSS
- MEDIUM 5.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-02
- Original CVE updated
- 2026-09-03
- Advisory published
- 2026-09-02
- Advisory updated
- 2026-09-03
Who should care
Defenders responsible for WordPress installations using the Wp Edit Password Protected plugin should assess exposure and prioritize verification and remediation efforts.
Why it matters
CVE-2025-8945 is a medium-severity vulnerability in the Wp Edit Password Protected WordPress plugin that allows bypassing page content protection using the REST API. Defenders should prioritize verifying exposure, monitoring for potential bypass attempts, and remediating vulnerable installations.
- Defenders need to verify if their WordPress installations are using the vulnerable plugin and are accessible via the REST API.
- Potential bypass attempts using the REST API require monitoring and logging.
- Remediation priority is moderate, as an update to version 1.3.5 or later is available.
Technical summary
The Wp Edit Password Protected WordPress plugin before version 1.3.5 allows protecting page content, but this protection can be bypassed by using the REST API. The vulnerability is a result of insufficient protection of page content, allowing unauthorized access to sensitive information. The plugin's protection mechanism can be bypassed using the REST API, which could lead to unauthorized access to sensitive information.
Defensive priority
Defenders should prioritize verifying exposure of WordPress installations using the Wp Edit Password Protected plugin, especially those allowing REST API access.
Recommended defensive actions
- Verify WordPress installations for the Wp Edit Password Protected plugin and ensure it is updated to version 1.3.5 or later.
- Restrict REST API access to trusted sources.
- Monitor for potential bypass attempts using the REST API.
Evidence notes
The CVE record and NVD entry provide limited information about the vulnerability. WPScan has identified the vulnerable plugin by name and version. The vulnerability was publicly disclosed on September 2, 2026. Defenders should verify if their WordPress installations are using the vulnerable plugin and are accessible via the REST API. Evidence is limited to CVE and NVD data.
Sources and references
Verified primary and authoritative sources
-
CVE-2025-8945 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2025-8945
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2025-8945 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2025-8945
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://wpscan.com/vulnerability/37cec6e0-a349-4cc7-971d-b370bc733ab6/
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.