CVE-2025-39422: WordPress WP Social Bookmarking plugin <= 3.6 - Cross Site Request Forgery (CSRF) vulnerability
Cross-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.
Security readout for executives and security teams
Plain-English summary
This is a high-severity issue in the WordPress WP Social Bookmarking plugin through version 3.6. A crafted request could cause a logged-in user to unintentionally store malicious content, creating stored cross-site scripting risk. The supplied sources do not identify a fixed version or confirm exploitation in the wild.
Executive priority
Treat as a near-term WordPress plugin risk. Prioritize sites using the affected plugin, especially public business sites with privileged editorial workflows. Urgency is high, but evidence does not support emergency active-exploitation language.
Technical view
CVE-2025-39422 is a CSRF flaw in PResponsive WP Social Bookmarking, package wp-social-bookmarking, reported as enabling stored XSS. CVSS 3.1 is 7.1 with network access, low complexity, no privileges, required user interaction, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure appears limited to WordPress sites running WP Social Bookmarking through version 3.6. The bundle does not provide install prevalence, fixed-version status, or configuration conditions beyond the affected plugin/version range.
Exploitation context
No supplied source or KEV status confirms active exploitation. The CVSS vector indicates an attacker needs user interaction but no prior privileges, so risk depends heavily on whether administrators or privileged users can be induced to perform an unsafe action.
Researcher notes
The source data has a notable gap: it states affected versions through 3.6 but does not provide patch availability or detailed vulnerable endpoint information. Avoid assuming exploitability details beyond CSRF leading to stored XSS.
Mitigation direction
Inventory WordPress sites for wp-social-bookmarking through version 3.6.
Check CVE, vendor, and Patchstack guidance for an official fixed version.
If no supported fix exists, disable or remove the plugin pending vendor guidance.
Review administrative accounts and stored plugin content for unexpected changes.
Validation and detection
Confirm whether WP Social Bookmarking is installed and active.
Record the installed plugin version across all WordPress sites.
Check whether any advisory names a fixed release after version 3.6.
Review recent content or settings changes tied to the plugin.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-352 · source CWE mapping
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.