CVE-2025-8427: Beaver Builder Plugin (Starter Version) <= 2.9.2.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'auto_play'
The Beaver Builder Team · Beaver Builder Plugin (Starter Version)
Affected: The Beaver Builder Team Beaver Builder Plugin (Starter Version) · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 7% of scored CVEs
DescriptionCVE.org
The Beaver Builder Plugin (Starter Version) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘auto_play’ parameter in all versions up to, and including, 2.9.2.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- The Beaver Builder Team · Beaver Builder Plugin (Starter Version)up to and including 2.9.2.1
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Weakness
- Cross-site Scripting
- Vendor
- The Beaver Builder Team
- Published
- October 2025
CoverageNo articles yet
No CyberSIXT article names CVE-2025-8427 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.