dbcve.org
Beaver BuilderWordPress extension · Fastlinemedia

CVE-2024-11832

MEDIUM · 5.4 CVSS v3.1 Published 2024-12-13
Fix available
A fix is available. Upgrade to 2.8.5.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
The Beaver Builder – WordPress Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the custom JavaScript row settings in all versions up to, and including, 2.8.4.4 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 confidence

The Beaver Builder plugin fails to properly sanitize and escape user input in the custom JavaScript row settings field. This allows authenticated users with Contributor-level access to inject malicious JavaScript that gets stored in the database and executes whenever other users view the affected pages.

MitigationUpdate the Beaver Builder plugin to version 2.8.4.5 or later. Until patched, restrict user permissions and review existing pages for suspicious custom JavaScript entries.

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.5.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. Confirm Beaver Builder plugin is installed
    Check WordPress plugins directory for 'beaver-builder' folder, or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if Beaver Builder plugin is not found in the installation
  2. Identify the installed Beaver Builder version
    Check the plugin header in beaver-builder-lite-version.php or beaver-builder.php file, or view the version listed in WordPress admin plugins page
    Affected if Installed version is lower than 2.8.5.3
  3. Check if custom JavaScript row settings are accessible
    In Beaver Builder editor, open any page for editing, click on a row settings, and look for a Custom JavaScript or Code field in the advanced tab
    Affected if Custom JavaScript field exists and accepts input in the row settings
  4. Inspect stored custom JavaScript entries
    Query the WordPress database: SELECT * FROM wp_postmeta WHERE meta_key LIKE '%custom_js%' OR meta_value LIKE '%<script%' (adjust wp_ prefix if different)
    Affected if Database contains entries in custom JavaScript fields with unsanitized script tags or suspicious JavaScript code

You are affected if Beaver Builder version is below 2.8.5.3 AND custom JavaScript fields are used on your site with untrusted contributor-level users having access.

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.5.3 or later
Fixed in 2.8.5.3
Interim mitigation

Update the Beaver Builder plugin to version 2.8.4.5 or later. Until patched, restrict user permissions and review existing pages for suspicious custom JavaScript entries.

Recommended fix High confidence

Beaver Builder 2.8.5.3

  1. 1. Back up your WordPress site and database before making any changes.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Find the Beaver Builder plugin in the list.
  5. 5. If an update is available, click 'Update Now' to update to the latest version (2.8.5.3 or later).
  6. 6. Alternatively, download the latest version from wordpress.org and upload it via Plugins > Add New > Upload Plugin.
  7. 7. After updating, verify the plugin version shows 2.8.5.3 or higher.
  8. 8. Clear any caching plugins or server-side caches.

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11832 — 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-11832 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