Beaver BuilderWordPress extension · Fastlinemedia
CVE-2025-8427
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Beaver Builder WordPress plugin (versions up to 2.9.2.1) contains a stored XSS vulnerability in the 'auto_play' parameter due to insufficient input sanitization and output escaping, allowing authenticated users with Contributor-level permissions to inject arbitrary JavaScript that executes when other users access affected pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Beaver BuilderWordPress extension
< 2.9.3.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Beaver Builder plugin versionLog into WordPress admin, go to Plugins > Installed Plugins, locate 'Beaver Builder Plugin (Pro or Lite)' and read the version number from the Version columnAffected if The installed version is lower than 2.9.3.1 (versions 2.9.2.1 and below are vulnerable)
-
Identify Beaver Builder layoutsIn WordPress admin, go to Pages or Posts and look for entries showing ' Beaver Builder' under the author column or having the Beaver Builder launch button visibleAffected if Any Beaver Builder layouts exist, the vulnerability could be present if the plugin version is vulnerable
-
Examine layout content for auto_play parameterEdit a Beaver Builder layout and inspect any video or media modules that may have an 'auto_play' setting. Check the module's advanced settings for any auto_play toggle or parameterAffected if The auto_play parameter exists in any video/media module and the plugin version is vulnerable
-
Check saved templates for auto_playGo to Beaver Builder > Templates in the admin sidebar and review saved templates for any video or media modules with auto_play configurationAffected if Saved templates contain auto_play settings and the plugin version is below 2.9.3.1
-
Inspect page source for injected scriptsView a published Beaver Builder page in a browser, right-click and select 'View Page Source', then search for script tags or suspicious JavaScript within video player embeds or media module outputAffected if Arbitrary script tags appear in the rendered output, indicating active exploitation of the stored XSS
You are affected if Beaver Builder plugin version is below 2.9.3.1 AND any Beaver Builder layouts with video/media modules using the auto_play parameter exist on your site.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.9.3.1
Update Beaver Builder plugin to version 2.9.3 or later which includes proper sanitization and output escaping for the affected parameter.
2.9.3.1
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the Beaver Builder plugin and click 'Update Now' to update to version 2.9.3.1 or later
- Alternatively, update via WP-CLI: wp plugin update beaver-builder
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Beaver Builder
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8427 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-8427 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data