Beaver BuilderWordPress extension · Fastlinemedia
CVE-2024-30425
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Beaver Builder Beaver Builder beaver-builder-lite-version allows DOM-Based XSS.This issue affects Beaver Builder: from n/a through <= 2.7.4.4.
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 · moderate confidenceDOM-Based XSS vulnerability in Beaver Builder lite version allows attackers to inject malicious scripts through unsanitized URL parameters that get rendered directly into the page DOM without proper encoding. The vulnerability exists in versions through 2.7.4.4 where user-controlled input reaches the DOM without sanitization.
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.7.4.5CVSS 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 versionNavigate to Plugins > Installed Plugins in WordPress admin, locate 'Beaver Builder Plugin' (Fastline Media), and note the installed version number. Alternatively, check the version in the plugin's main PHP file header.Affected if The installed version is lower than 2.7.4.5 (e.g., 2.7.4.4, 2.7.4.3, etc.)
-
Identify frontend JavaScript handling URL parametersInspect the Beaver Builder plugin files, specifically looking in the /js or /assets/js directory for JavaScript files that read URL parameters using functions like window.location.href, URLSearchParams, or $_GET that output directly to the DOM.Affected if JavaScript code reads URL parameters and inserts them into the DOM using innerHTML, document.write, or similar methods without encoding/sanitization
-
Test URL parameter reflection in the DOMWith Beaver Builder active, access a frontend page built with Beaver Builder and append a test parameter (e.g., ?testparam=<img src=x onerror=alert(1)>) to the URL. View the page source or inspect the DOM to see if the parameter value is rendered unsanitized.Affected if The URL parameter value appears in the DOM without HTML encoding (e.g., the literal <img src=x onerror=alert(1)> string is present rather than its HTML-encoded equivalent)
You are affected if your installed Beaver Builder version is below 2.7.4.5 AND your site processes URL parameters that get rendered directly into the page DOM without sanitization.
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.7.4.5
Update to a patched version of Beaver Builder. Until then, implement output encoding when handling URL parameters in JavaScript and validate/sanitize any user input before DOM insertion.
2.7.4.5
- 1. Back up your WordPress site before making any changes
- 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- 3. Find Beaver Builder (or Beaver Builder Lite) in the plugin list
- 4. If an update is available, click 'Update Now' to upgrade to version 2.7.4.5
- 5. Alternatively, manually upload version 2.7.4.5 of Beaver Builder via Plugins > Add New > Upload Plugin
- 6. After updating, verify the plugin version shows 2.7.4.5
- 7. Test the site functionality to confirm the update works correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Beaver Builder
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30425 — 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-2024-30425 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