CVE-2025-23435
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-Site Request Forgery (CSRF) vulnerability in marcucci Password Protect Plugin for WordPress password-protect-plugin-for-wordpress allows Stored XSS.This issue affects Password Protect Plugin for WordPress: from n/a through <= 0.8.1.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA Cross-Site Request Forgery (CSRF) vulnerability in the Password Protect Plugin for WordPress (versions up to 0.8.1.0) allows authenticated administrators to be tricked into performing unintended actions that result in Stored XSS. This combined attack vector is particularly dangerous as the malicious payload persists on the site and executes when other users visit affected pages, potentially leading to session hijacking and privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed plugin versionNavigate to WordPress admin > Plugins > Installed Plugins. Locate 'Password Protect Plugin' or similar named plugin. The version number is displayed below the plugin name.Affected if The installed version is 0.8.1.0 or any version up to 0.8.1.0 (e.g., 0.7.0, 0.6.5, etc.).
-
Verify plugin is activeIn the Plugins list, confirm the 'Password Protect Plugin' shows as 'Active'. The vulnerability only affects sites where the plugin is enabled.Affected if The plugin is active on the WordPress site.
-
Identify vulnerable plugin filesCheck the plugin directory (wp-content/plugins/) for the Password Protect Plugin folder. Examine PHP files for form handling and AJAX endpoints. Look for the absence of nonce validation or CSRF token checks in form processing code.Affected if Plugin forms or AJAX actions lack CSRF token validation (wp_nonce_field, check_ajax_referer, or similar functions are missing).
You are affected if the Password Protect Plugin is active and running at version 0.8.1.0 or below, as this version lacks CSRF protection on forms and allows Stored XSS payloads to be injected.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the plugin to the latest version if available. As an interim measure, ensure admin sessions are protected and consider disabling the plugin until a patch is applied. The fix requires implementing CSRF tokens on all forms and AJAX endpoints, plus proper output escaping to prevent XSS.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23435 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-23435 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data