Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Buooy Buooy Sticky Header buooy-sticky-header allows Reflected XSS.This issue affects Buooy Sticky Header: from n/a through <= 0.5.2.
Security readout for executives and security teams
Plain-English summary
CVE-2024-51699 is a reflected cross-site scripting flaw in the WordPress Buooy Sticky Header plugin through version 0.5.2. A successful attack would require a user to interact with a crafted link or page, but could affect confidentiality, integrity, and availability at a limited level.
Executive priority
Treat this as a near-term web security cleanup item for any WordPress estate. Prioritize public sites and sites with administrator traffic, but avoid emergency assumptions because the provided sources do not confirm active exploitation.
Technical view
The issue is CWE-79 improper neutralization of input during web page generation in buooy-sticky-header. The CVSS 3.1 score is 7.1: network reachable, low complexity, no privileges required, user interaction required, and changed scope.
Likely exposure
Exposure is limited to WordPress sites that have the Buooy Sticky Header plugin installed at version 0.5.2 or earlier. Sites without this plugin are not indicated as affected by the source bundle.
Exploitation context
The source bundle does not show CISA KEV listing or other evidence of active exploitation. Risk remains meaningful because reflected XSS can be triggered through user interaction on public-facing WordPress sites.
Researcher notes
Evidence is incomplete for endpoint details, exploit maturity, and fixed-version status. The strongest source-grounded facts are the affected plugin range through 0.5.2, reflected XSS classification, CVSS vector, and lack of KEV status.
Mitigation direction
Inventory WordPress sites for the Buooy Sticky Header plugin.
Identify any installations at version 0.5.2 or earlier.
Check vendor, CVE, and Patchstack guidance for a fixed version.
Update if a fixed release is available from trusted sources.
Disable or remove the plugin if no safe update is available.
Validation and detection
Confirm plugin presence and exact version on each WordPress site.
Run vulnerability scanner checks for CVE-2024-51699 where available.
Review web logs for suspicious requests involving the plugin.
Verify remediation by rescanning affected WordPress instances.
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-79: 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-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.