dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-2481

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 Page Builder – Drag and Drop Website Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'settings[js]' parameter in versions up to, and including, 2.10.1.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-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 · moderate confidence

The Beaver Builder Page Builder plugin for WordPress is vulnerable to stored Cross-Site Scripting (XSS) via the 'settings[js]' parameter in versions up to 2.10.1.1. The vulnerability stems from insufficient input sanitization and insufficient output escaping, allowing authenticated attackers with author-level permissions or higher to inject arbitrary JavaScript that executes whenever users access compromised pages.

MitigationUpdate the Beaver Builder plugin to the latest version beyond 2.10.1.1, which should contain proper sanitization for the 'settings[js]' parameter and appropriate output escaping. Additionally, review existing pages for malicious script injections and consider restricting user permissions to the minimum required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 is installed
    Navigate to WordPress admin > Plugins and confirm 'Beaver Builder Page Builder' is active, or use command: wp plugin list --name='beaver-builder' --format=table
    Affected if Plugin is installed and active
  2. Check installed Beaver Builder version
    In WordPress admin > Plugins, click 'View Details' on Beaver Builder to see version number, or run: wp plugin get beaver-builder --field=version
    Affected if Version is 2.10.1.1 or earlier (any version up to and including 2.10.1.1)
  3. Identify users with author-level or higher permissions
    Go to WordPress admin > Users and review user roles, or query database: SELECT user_id, meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%author%' (adjust prefix if wp_ is different)
    Affected if Any user account has author, editor, or administrator role
  4. Inspect stored 'settings[js]' parameter in database
    Query the Beaver Builder settings tables (typically in wp_postmeta with meta_key containing 'fl_builder_settings' or similar) for any rows containing 'settings' with a 'js' key: SELECT * FROM wp_postmeta WHERE meta_key LIKE '%fl_builder%settings%'
    Affected if Records exist with 'settings' field containing JavaScript or script tags that were not properly sanitized on output

User is affected if Beaver Builder version is 2.10.1.1 or earlier AND author-level or higher user accounts exist in WordPress AND malicious JavaScript has been injected via the settings[js] parameter in stored plugin settings.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Beaver Builder plugin to the latest version beyond 2.10.1.1, which should contain proper sanitization for the 'settings[js]' parameter and appropriate output escaping. Additionally, review existing pages for malicious script injections and consider restricting user permissions to the minimum required.

Recommended fix Moderate confidence

Latest stable Beaver Builder release (version higher than 2.10.1.1)

  1. Check your currently installed Beaver Builder plugin version in WordPress admin under Plugins
  2. If your version is 2.10.1.1 or lower, navigate to Plugins > Add New > Upload Plugin or use the WordPress plugin repository to update to the latest version
  3. After updating, verify the plugin is functioning correctly on your site
  4. Test that the settings[js] parameter is now properly sanitized if you need to use custom JavaScript settings
  5. Consider reviewing user accounts and removing any unauthorized malicious scripts that may have been injected during any potential exploitation
Caveat Standard plugin update - review any custom templates or JavaScript snippets for compatibility with the new version

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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