Contributor-triggered script execution in privileged users' browsers
Published Nov 19, 2024 · Updated May 11, 2026
Stored XSS in Beaver Builder 2.8.3.7 and earlier allows remote authenticated users to execute script in a privileged user's browser via saved content. Patchstack has not published the affected input, module, code path, or incorrect neutralization operation, leaving the underlying mechanism undisclosed. Contributor-level access is required to store the payload, and exploitation also requires a privileged user to open the affected content.
Summary
What happened
Stored XSS in Beaver Builder 2.8.3.7 and earlier allows remote authenticated users to execute script in a privileged user's browser via saved content. Patchstack has not published the affected input, module, code path, or incorrect neutralization operation, leaving the underlying mechanism undisclosed. Contributor-level access is required to store the payload, and exploitation also requires a privileged user to open the affected content.
The record
- CVE
- CVE-2024-50430
- Published
- Nov 19, 2024
- Updated
- May 11, 2026
- Vendor
- Beaver Builder
- Product
- Beaver Builder
- Classifications
- CWE-79, CAPEC-592, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 19, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.8.3.7 changes=[{"at":"2.8.3.9","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo