CVE-2025-39422
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 PResponsive WP Social Bookmarking wp-social-bookmarking allows Stored XSS.This issue affects WP Social Bookmarking: from n/a through <= 3.6.
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 WP Social Bookmarking WordPress plugin (versions <= 3.6) allows attackers to inject malicious scripts through stored XSS. An attacker can trick an authenticated administrator into clicking a crafted link, causing malicious JavaScript to be stored in the plugin's settings and executed when other users view affected pages.
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 if WP Social Bookmarking plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'WP Social Bookmarking' in the listAffected if The plugin appears in the installed plugins list
-
Verify the installed version numberIn the Plugins list, find WP Social Bookmarking and check the version number displayed beneath the plugin name (e.g., 'Version 3.6' or lower)Affected if The installed version is 3.6 or any version lower than 3.6
-
Confirm the plugin is activeIn the Plugins list, check if WP Social Bookmarking shows 'Active' status rather than 'Inactive' or 'Must-Use'Affected if The plugin is currently activated on the site
-
Inspect plugin settings for stored scriptsGo to plugin settings page (usually Settings > WP Social Bookmarking or similar) and examine any text fields where social sharing buttons or custom messages are configured. Look for unexpected <script> tags, javascript: URLs, or encoded script content in saved valuesAffected if Any settings fields contain suspicious JavaScript code, encoded payloads, or unexpected HTML/script content that was not intentionally configured by an administrator
-
Check database for malicious stored valuesAccess the WordPress database (via phpMyAdmin or wp CLI) and query the wp_options table for option_name like '%wp_social%' or '%social_bookmarking%'. Examine option_value fields for script tags, event handlers (onload, onerror, onclick), or encoded JavaScriptAffected if Database option values contain script elements or JavaScript event handlers that were not deliberately added by site administrators
A site is affected if WP Social Bookmarking plugin is installed at version 3.6 or lower, is active, and contains unexpected script content in its settings or database entries.
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 to a patched version of WP Social Bookmarking when available; alternatively, disable the plugin. Implement anti-CSRF tokens on all state-changing forms and ensure proper input sanitization and output encoding for stored data.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-39422 — 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-39422 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