dbcve.org
Beaver BuilderWordPress extension · Fastlinemedia

CVE-2024-37500

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-21
Fix available
A fix is available. Upgrade to 2.8.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in The Beaver Builder Team Beaver Builder allows Stored XSS.This issue affects Beaver Builder: from n/a through 2.8.2.2.

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 confidence

Beaver Builder plugin versions up to 2.8.2.2 contain a Stored XSS vulnerability where user-supplied input is improperly neutralized during web page generation, allowing attackers to embed malicious scripts that execute when other users view the affected content.

MitigationUpdate Beaver Builder to the latest patched version immediately. Review existing Beaver Builder content and user inputs for signs of compromise since Stored XSS payloads may have been injected prior to patching.

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
Affected:< 2.8.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Beaver Builder installed version
    Navigate to WordPress admin > Plugins and locate 'Beaver Builder' in the plugin list. The version number is displayed below the plugin name. Alternatively, inspect the main plugin file (typically /wp-content/plugins/bb-plugin/ or /wp-content/plugins/beaver-builder-lite-version/) and look for version information in the plugin header comment.
    Affected if The installed version is any version prior to 2.8.3 (including 2.8.2.2, 2.8.2.1, 2.8.2, 2.8.1, and earlier releases).
  2. Identify Beaver Builder content types in use
    Review your WordPress pages and posts that were created or edited using the Beaver Builder editor. Check the wp_posts table in the database for posts where post_content contains 'fl-builder' shortcodes or meta data indicates Beaver Builder was used.
    Affected if Any Beaver Builder content exists on the site, as the vulnerability affects how user input is rendered in Beaver Builder-generated pages.
  3. Inspect saved Beaver Builder layouts and rows
    Access the Beaver Builder templates or saved rows/modules through the WordPress admin. Navigate to Beaver Builder > Templates (or check the wp_postmeta table for fl_builder_data meta_key entries) to view stored Beaver Builder configurations.
    Affected if Any custom rows, modules, or templates are saved within Beaver Builder, as these may contain unsanitized user-supplied attributes.
  4. Search for suspicious script injections in content
    Query the WordPress database (wp_posts and wp_postmeta tables) for common XSS patterns: script tags, javascript: URLs, event handlers (onload, onerror, onmouseover), and base64-encoded payloads. Search for <script, onmouseover=, onerror=, data: in post content and meta values.
    Affected if Any suspicious script tags or event handlers are found in Beaver Builder-related content or metadata, indicating possible exploitation.

Your environment is affected if Beaver Builder version is below 2.8.3 and you have any Beaver Builder content or saved layouts on your site that could contain user-supplied input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.8.3 or later
Fixed in 2.8.3
Interim mitigation

Update Beaver Builder to the latest patched version immediately. Review existing Beaver Builder content and user inputs for signs of compromise since Stored XSS payloads may have been injected prior to patching.

Recommended fix High confidence

Beaver Builder version 2.8.3

  1. 1. Back up your WordPress site and database before performing any updates.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Find the Beaver Builder plugin and check for available updates.
  5. 5. Update Beaver Builder to version 2.8.3 or later.
  6. 6. After updating, clear any caching plugins you may have active.
  7. 7. Verify the update was successful by checking the plugin version in Plugins > Installed Plugins.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Beaver Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-37500 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-37500 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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