CVE-2025-8427: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in The Beaver Builder Team Beaver Builder Plugin (Starter Version)
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.
AI Analysis
Technical Summary
The Beaver Builder Plugin (Starter Version) for WordPress contains a stored cross-site scripting vulnerability identified as CVE-2025-8427. This vulnerability is due to improper neutralization of input during web page generation, specifically insufficient sanitization and escaping of the 'auto_play' parameter. Authenticated attackers with Contributor-level privileges or higher can inject malicious scripts that persist in pages and execute in the context of users who visit those pages. This can lead to limited confidentiality and integrity impacts as indicated by the CVSS vector (Confidentiality and Integrity impact: Low; Availability: None). The vulnerability affects all versions up to 2.9.2.1. No patch or remediation details are currently available from the vendor or advisory sources.
Potential Impact
An attacker with Contributor-level or higher access can exploit this vulnerability to inject stored malicious scripts via the 'auto_play' parameter. These scripts execute in the browsers of users who view the compromised pages, potentially leading to limited confidentiality and integrity impacts such as session hijacking or content manipulation. There is no impact on availability. No known exploits have been reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict Contributor-level access to trusted users only and consider implementing additional input validation or output encoding controls at the application or web server level to mitigate risk. Monitor vendor channels for updates and apply patches promptly once released.
CVE-2025-8427: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in The Beaver Builder Team Beaver Builder Plugin (Starter Version)
Description
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Beaver Builder Plugin (Starter Version) for WordPress contains a stored cross-site scripting vulnerability identified as CVE-2025-8427. This vulnerability is due to improper neutralization of input during web page generation, specifically insufficient sanitization and escaping of the 'auto_play' parameter. Authenticated attackers with Contributor-level privileges or higher can inject malicious scripts that persist in pages and execute in the context of users who visit those pages. This can lead to limited confidentiality and integrity impacts as indicated by the CVSS vector (Confidentiality and Integrity impact: Low; Availability: None). The vulnerability affects all versions up to 2.9.2.1. No patch or remediation details are currently available from the vendor or advisory sources.
Potential Impact
An attacker with Contributor-level or higher access can exploit this vulnerability to inject stored malicious scripts via the 'auto_play' parameter. These scripts execute in the browsers of users who view the compromised pages, potentially leading to limited confidentiality and integrity impacts such as session hijacking or content manipulation. There is no impact on availability. No known exploits have been reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict Contributor-level access to trusted users only and consider implementing additional input validation or output encoding controls at the application or web server level to mitigate risk. Monitor vendor channels for updates and apply patches promptly once released.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-07-31T17:54:38.284Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68fa270960d00e69dc99fa71
Added to database: 10/23/2025, 1:00:57 PM
Last enriched: 4/9/2026, 10:53:07 AM
Last updated: 5/10/2026, 5:24:31 AM
Views: 275
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.