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

CVE-2026-34889

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/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 ('Cross-site Scripting') vulnerability in Brainstorm Force Ultimate Addons for WPBakery Page Builder allows DOM-Based XSS.This issue affects Ultimate Addons for WPBakery Page Builder: from n/a before 3.21.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 · high confidence

DOM-Based XSS vulnerability in the Ultimate Addons for WPBakery Page Builder plugin allows attackers to inject malicious scripts through improper input neutralization in web page generation. The flaw exists in versions prior to 3.21.4.

MitigationUpgrade Ultimate Addons for WPBakery Page Builder to version 3.21.4 or later to patch the XSS vulnerability. Test thoroughly after upgrade to ensure plugin functionality remains intact.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L

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 plugin installation and version
    Locate the Ultimate Addons for WPBakery Page Builder in your WordPress plugins directory or check the plugin admin panel for the installed version number
    Affected if The plugin version shown is lower than 3.21.4 or the version cannot be determined
  2. Compare version against affected range
    Review the installed version number and compare it to the vulnerable range: any version prior to 3.21.4
    Affected if The installed version begins with a number lower than 3.21.4 (for example, 3.21.3, 3.20.x, or earlier)
  3. Confirm WPBakery Page Builder is active
    Check if WPBakery Page Builder core plugin is enabled, as the Ultimate Addons plugin extends its functionality
    Affected if WPBakery Page Builder is active and the Ultimate Addons version is below 3.21.4
  4. Identify frontend content using the plugin
    Review pages or posts created using the Ultimate Addons widgets, particularly those that accept user input or render dynamic content
    Affected if The plugin is actively used to generate pages or post content and the version is below 3.21.4

You are affected if the Ultimate Addons for WPBakery Page Builder plugin is installed with any version prior to 3.21.4 and is used to render frontend content.

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

Upgrade Ultimate Addons for WPBakery Page Builder to version 3.21.4 or later to patch the XSS vulnerability. Test thoroughly after upgrade to ensure plugin functionality remains intact.

Recommended fix Moderate confidence

Ultimate Addons for WPBakery Page Builder version 3.21.4

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate 'Ultimate Addons for WPBakery Page Builder' by Brainstorm Force
  4. 4. Check the current installed version number
  5. 5. If the installed version is before 3.21.4, update the plugin to version 3.21.4 or later
  6. 6. Verify the update completed successfully
  7. 7. Clear any caching mechanisms (site cache, CDN cache) after updating
  8. 8. Test the affected functionality to confirm the XSS vulnerability is remediated

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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