dbcve.org
Beaver BuilderWordPress extension · Fastlinemedia

CVE-2024-3923

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to after 2.8.1.2 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 link_target parameter in all versions up to, and including, 2.8.1.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor access or higher, 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 WordPress Page Builder plugin versions up to 2.8.1.1 are vulnerable to stored XSS via the link_target parameter due to insufficient input sanitization on entry and inadequate output escaping on display. Authenticated users with contributor-level permissions or higher can inject malicious JavaScript that executes when other users view the affected pages.

MitigationUpdate Beaver Builder plugin to version 2.8.1.2 or later, which includes proper sanitization of the link_target parameter and correct output escaping. Review existing pages for injected scripts.

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.1.2

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. Verify Beaver Builder plugin version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, locate 'Beaver Builder Plugin (formerly Fastline Media Beaver Builder)' and check the version number displayed
    Affected if Installed version is 2.8.1.2 or lower
  2. Identify contributor-level or higher users
    Go to WordPress admin > Users and review user roles. Look for accounts with Contributor, Author, Editor, or Administrator roles
    Affected if Any user account with contributor-level or higher permissions exists on the site
  3. Inspect page content for link_target usage
    Access WordPress database via phpMyAdmin or CLI. Query the wp_posts table for Beaver Builder module data containing 'link_target' in post_content or postmeta tables where meta_key includes link_target values
    Affected if Database contains Beaver Builder content modules using the link_target parameter
  4. Analyze stored link_target values for malicious code
    Export or examine the link_target field values from Beaver Builder module data in the database. Look for patterns like 'javascript:', event handlers (onclick, onload, onerror), or script tags within these values
    Affected if Any link_target parameter contains unsanitized HTML, JavaScript protocols, or event handler attributes

A user is affected if Beaver Builder plugin version is 2.8.1.2 or lower AND any contributor-level user has created Beaver Builder content with a link_target parameter containing malicious script injection.

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 a release after 2.8.1.2
Interim mitigation

Update Beaver Builder plugin to version 2.8.1.2 or later, which includes proper sanitization of the link_target parameter and correct output escaping. Review existing pages for injected scripts.

Recommended fix High confidence

Beaver Builder version 2.8.1.2 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Beaver Builder plugin
  4. 4. Check the current version number to confirm it is 2.8.1.1 or earlier
  5. 5. If an update is available, click 'Update Now' to upgrade to version 2.8.1.2 or later
  6. 6. Alternatively, navigate to Dashboard > Updates and update the Beaver Builder plugin from there
  7. 7. After updating, clear any caching plugins if present
  8. 8. Verify the update was successful by checking the plugin version

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
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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