CVE-2025-8427: Beaver Builder Plugin (Starter Version) <= 2.9.2.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'auto_play'
The Beaver Builder Plugin (Starter Version) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘autoplay’ 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 Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-8427?
CVE-2025-8427 is considered a critical vulnerability due to the potential for Stored Cross-Site Scripting which can lead to significant security risks.
How do I fix CVE-2025-8427?
To fix CVE-2025-8427, update the Beaver Builder Plugin (Starter Version) to version 2.9.2.2 or higher.
What causes the vulnerability in CVE-2025-8427?
CVE-2025-8427 is caused by insufficient input sanitization and output escaping of the 'auto_play' parameter.
Who is affected by CVE-2025-8427?
All users of the Beaver Builder Plugin (Starter Version) up to version 2.9.2.1 are affected by CVE-2025-8427.
What is the impact of CVE-2025-8427?
The impact of CVE-2025-8427 can allow attackers to inject malicious scripts into web pages viewed by users, potentially compromising user data.