CVE-2025-58670
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 Shankaranand Maurya WP Content Protection wp-content-protection allows Stored XSS.This issue affects WP Content Protection: from n/a through <= 1.3.
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 WP Content Protection WordPress plugin (versions <= 1.3) allows authenticated administrators to be tricked into submitting malicious requests that inject persistent XSS payloads into the application, which then execute when other users view the compromised content.
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.
-
Verify WP Content Protection plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'WP Content Protection' in the list of active plugins.Affected if Plugin is present and active in the WordPress installation
-
Check installed plugin versionIn the Plugins list, click on the plugin name to view details, or inspect the plugin header in wp-content/plugins/wp-content-protection/wp-content-protection.php for the 'Version' comment.Affected if Version number displayed is 1.3 or lower
-
Confirm plugin handles admin state-changing operationsReview the plugin settings pages under the WP Content Protection menu in the admin dashboard. Look for any forms that modify content protection rules, user permissions, or content configurations.Affected if Plugin provides admin interface forms that modify plugin settings or content protection rules
-
Inspect plugin source for CSRF protectionExamine the plugin PHP files (particularly form handlers and admin action callbacks) for the presence of nonce verification using wp_verify_nonce(), check_admin_referer(), or similar WordPress nonce functions.Affected if No nonce verification is found in state-changing admin action handlers, or nonce checks are missing entirely
User is affected if WP Content Protection plugin version 1.3 or lower is installed and the plugin handles admin form submissions without proper CSRF token validation.
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 WP Content Protection plugin to a version beyond 1.3 that implements proper CSRF token validation (nonces) for all state-changing operations and output encoding to prevent stored XSS.
- Consultation2.0 h
- Implementation6.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58670 — 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-58670 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