Contributor-level stored XSS
Published Jul 21, 2024 · Updated Apr 28, 2026
Stored XSS in Beaver Builder 2.8.2.2 and earlier allows remote authenticated users to inject scripts into WordPress pages. Patchstack has not published the affected input field or code path, identifying only stored script injection into page content that executes on later visits. Contributor-level access is required, and exploitation also requires another user to visit the affected page; the script then executes in that visitor's browser context.
Summary
What happened
Stored XSS in Beaver Builder 2.8.2.2 and earlier allows remote authenticated users to inject scripts into WordPress pages. Patchstack has not published the affected input field or code path, identifying only stored script injection into page content that executes on later visits. Contributor-level access is required, and exploitation also requires another user to visit the affected page; the script then executes in that visitor's browser context.
The record
- CVE
- CVE-2024-37500
- Published
- Jul 21, 2024
- Updated
- Apr 28, 2026
- Vendor
- Beaver Builder
- Product
- Beaver Builder
- Classifications
- CWE-79, CAPEC-592, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 21, 2024CVE publishedPublication date reported by the CVE source.
- Apr 28, 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=n/a <=2.8.2.2 changes=[{"at":"2.8.3","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