A notable security flaw has been identified in the Beaver Builder Plugin (Starter Version) for WordPress. This vulnerability, tracked as CVE-2025-8427, is a Stored Cross-Site Scripting (XSS) issue. It stems from inadequate input handling and output encoding related to the \u2018auto_play\u2019 parameter within the plugin.<\/p>\n
In simple terms, this means that if you’re using an affected version of the Beaver Builder plugin, an authenticated attacker\u2014someone with at least Contributor-level access to your WordPress site\u2014could sneak malicious code into your website. This hidden code would then run whenever another user visits a page where the code has been injected, potentially leading to unauthorized actions or data theft.<\/p>\n
The Stored Cross-Site Scripting vulnerability affects the Beaver Builder Plugin (Starter Version) for WordPress in all versions up to, and including, 2.9.2.1.<\/p>\n
This vulnerability has been thoroughly analyzed, confirming its existence and potential impact on websites utilizing the affected plugin versions. Users are advised to take prompt action to secure their installations.<\/p>\n
Rated as “Medium” severity with a CVSS score of 6.4, this vulnerability requires an attacker to have prior authentication to your WordPress site, specifically Contributor-level access or higher. While this access requirement lowers the immediate risk compared to vulnerabilities exploitable by unauthenticated users, the impact can still be significant. Successful exploitation could lead to defacement, redirection, session hijacking, or even further compromise of the website or its users. Understanding the potential risks is a crucial part of WordPress security best practices<\/a>.<\/p>\n The good news is that a fix for this vulnerability is available. Users of the Beaver Builder Plugin (Starter Version) should update their installations immediately to version 2.9.3 or newer<\/strong>. According to the change logs, version 2.9.3 was released on August 14, 2025, and specifically addresses an XSS issue related to the “auto play” setting in the Testimonials Module, which aligns with the reported vulnerability.<\/p>\n Regularly updating your plugins is a fundamental step in maintaining a secure WordPress environment. For more information on preventing similar attacks, consider learning about understanding Cross-Site Scripting<\/a>.<\/p>\n https:\/\/www.wordfence.com\/threat-intel\/vulnerabilities\/id\/afec9b5b-da37-4e12-935e-9d3bb3ca01f0?source=cve<\/p>\nPossible Solutions<\/h2>\n
References<\/h2>\n