Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Beaver Builder Beaver Builder beaver-builder-lite-version allows Stored XSS.This issue affects Beaver Builder: from n/a through <= 2.8.3.7.
Security readout for executives and security teams
Plain-English summary
CVE-2024-50430 is a stored cross-site scripting issue in the WordPress Beaver Builder plugin through version 2.8.3.7. An attacker with high privileges could store unsafe content that later runs in another user’s browser. Business risk is moderate because exploitation requires privileges and user interaction, but affected websites should still be checked promptly.
Executive priority
Handle in the normal vulnerability management cycle with prompt attention for public WordPress properties. Prioritize sites where many users or administrators view Beaver Builder-managed content, because stored XSS can support account abuse or content tampering if triggered.
Technical view
The CVE describes CWE-79 improper input neutralization during web page generation in Beaver Builder beaver-builder-lite-version. CVSS 3.1 score is 6.5 with AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L. Scope change means browser-executed script may affect another security context, but sources do not provide payload details or a confirmed fixed version.
Likely exposure
Exposure is likely limited to WordPress sites running Beaver Builder beaver-builder-lite-version at versions through 2.8.3.7. Sites without the plugin, or running versions outside the affected range per vendor guidance, are not indicated as affected by the provided sources.
Exploitation context
The bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates exploitation is network reachable, low complexity, requires high privileges, and needs user interaction. Treat exploit status as unconfirmed from the provided evidence.
Researcher notes
Do not assume public exploit availability or a fixed version from this bundle. The key constraints are PR:H and UI:R, with changed scope and low confidentiality, integrity, and availability impacts. Validation should focus on plugin presence, affected version range, and vendor-confirmed remediation status.
Mitigation direction
Inventory WordPress sites for Beaver Builder beaver-builder-lite-version installations.
Treat versions through 2.8.3.7 as affected until vendor guidance says otherwise.
Check Beaver Builder and Patchstack guidance for the fixed version or official remediation.
Restrict high-privilege WordPress accounts to trusted users only.
Review recent privileged content changes on affected sites.
Validation and detection
Confirm the plugin slug and installed Beaver Builder version on each WordPress site.
Compare installed versions against the affected range through 2.8.3.7.
Check whether vendor or Patchstack guidance identifies a remediated release.
Review administrative activity for unexpected page or layout modifications.
Document whether each site is affected, remediated, or not applicable.
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.