CVE-2024-51631: WordPress Sticky Social Bar plugin <= 2.0 - CSRF to Stored Cross Site Scripting (XSS) vulnerability
Cross-Site Request Forgery (CSRF) vulnerability in Md Eftakhairul Islam Sticky Social Bar sticky-social-bar allows Cross Site Request Forgery.This issue affects Sticky Social Bar: from n/a through <= 2.0.
Security readout for executives and security teams
Plain-English summary
CVE-2024-51631 affects the WordPress Sticky Social Bar plugin through version 2.0. A malicious site could trick a logged-in WordPress user into making an unwanted change that stores script content. That could expose visitors or administrators to browser-based compromise, depending on site role and configuration.
Executive priority
Treat this as high priority for WordPress estates using the plugin, especially public sites with privileged administrators. Prioritize inventory and remediation confirmation over broad emergency action because the provided sources do not show active exploitation.
Technical view
The sources describe a CSRF issue in Md Eftakhairul Islam Sticky Social Bar, reported as CSRF leading to stored XSS. CVSS 3.1 is 7.1 high with network attack vector, low complexity, no attacker privileges, required user interaction, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to WordPress sites with the Sticky Social Bar plugin installed at version 2.0 or earlier. The bundle does not identify other affected products, CPEs, or a confirmed fixed version.
Exploitation context
The provided bundle does not show CISA KEV listing or cite active exploitation. Exploitation requires user interaction, consistent with CSRF, and appears to depend on a logged-in WordPress user being induced to trigger an unwanted state-changing action.
Researcher notes
Evidence is concise: CVE metadata and Patchstack identify CSRF to stored XSS in Sticky Social Bar through 2.0. The bundle does not provide exploit detail, vulnerable endpoint detail, proof-of-concept status, or fixed-version information, so validation should remain source-bound and non-invasive.
Mitigation direction
Inventory WordPress sites for the Sticky Social Bar plugin and version.
Check vendor and Patchstack guidance for a fixed release or official remediation.
Update the plugin if a trusted fixed version is available.
Deactivate or remove the plugin where remediation cannot be confirmed.
Review WordPress administrative access and reduce unnecessary privileged sessions.
Validation and detection
Confirm whether Sticky Social Bar is installed on each WordPress site.
Verify installed versions are not 2.0 or older.
Check plugin settings or stored content for unexpected script-like changes.
Review WordPress audit logs for suspicious administrative setting updates.
Confirm current KEV status before prioritizing emergency response.
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.