CVE-2025-23875
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 madeglobal Better Protected Pages better-protected-pages allows Stored XSS.This issue affects Better Protected Pages: from n/a through <= 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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Better Protected Pages plugin allows unauthenticated attackers to trick authenticated administrators into performing unintended actions that inject malicious JavaScript (Stored XSS). The lack of anti-CSRF tokens on state-changing form submissions enables this attack vector.
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.
-
Confirm Better Protected Pages plugin installationNavigate to WordPress admin dashboard > Plugins and locate 'Better Protected Pages' in the installed plugins list, or check for the plugin directory at /wp-content/plugins/Affected if The plugin is installed and active in the WordPress environment
-
Identify the installed plugin versionIn the WordPress Plugins admin page, click the plugin name to view version details, or read the Version header from the main plugin file (typically better-protected-pages.php)Affected if The installed version falls within the affected range once the vendor discloses specific vulnerable versions
-
Inspect admin forms for anti-CSRF token presenceView the HTML source of the plugin admin pages and examine all state-changing forms (settings pages, save buttons, configuration updates) for hidden input fields containing nonce values such as wp_nonce, _wpnonce, or nonce_fieldAffected if State-changing forms in the plugin admin area lack nonce or anti-CSRF token fields entirely
-
Verify nonce validation on form processingExamine the plugin PHP source code (typically in the admin handler or form processing functions) to confirm that wp_verify_nonce or check_admin_referer is called before processing any POST requests that modify plugin settingsAffected if The plugin code does not verify anti-CSRF tokens before processing admin form submissions
The environment is affected if the Better Protected Pages plugin is installed and its admin forms process state-changing requests without validating anti-CSRF (nonce) tokens.
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 dataImplement WordPress nonces (anti-CSRF tokens) on all admin form submissions and POST requests, and ensure all user-supplied input is properly sanitized before storage and escaped before output. Users should update to a patched version when released.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23875 — 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-23875 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