dbcve.org
Page BuilderWordPress extension · Wpbakery

CVE-2024-1805

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-02
Fix available
A fix is available. Upgrade to 7.6 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 wpbakery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the button onclick attribute in all versions up to, and including, 7.5 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 WPBakery page builder plugin for WordPress versions up to 7.5 is vulnerable to stored cross-site scripting (XSS) via the button onclick attribute. Authenticated attackers with contributor-level access or higher can inject malicious JavaScript through insufficient input sanitization that is not properly escaped upon output, causing scripts to execute when users access compromised pages.

MitigationUpdate WPBakery page builder to version 7.6 or later. Until patched, limit user registration to trusted roles only and consider implementing Content Security Policy headers to mitigate XSS execution.

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
Page BuilderWordPress extension
Affected:< 7.6

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 WPBakery Page Builder version
    In WordPress admin, go to Plugins > Installed Plugins > WPBakery Page Builder and read the Version number. Alternatively, check the plugin header in /wp-content/plugins/js_composer/include/classes/core/class-wpb-map.php or the main plugin file.
    Affected if Version is below 7.6 (any version up to and including 7.5)
  2. Verify if contributor-level or higher users exist
    Navigate to WordPress admin > Users and review user accounts. Check the Role column for any users with Contributor, Author, Editor, or Administrator roles that may belong to untrusted parties.
    Affected if Any untrusted user with Contributor, Author, or higher role exists on the site
  3. Inspect posts/pages for malicious onclick attributes
    Search the WordPress database (wp_posts table) or export content and search for 'onclick=' strings within button elements or VC elements. Use SQL: SELECT * FROM wp_posts WHERE post_content LIKE '%onclick=%';
    Affected if Any button element or Visual Composer element contains suspicious or encoded onclick attributes
  4. Review recent content edits by contributor-level users
    In WordPress admin, check Posts or Pages edited recently. Look for custom button elements or link elements where onclick JavaScript may have been injected. Focus on content created by users with Contributor or Author roles.
    Affected if Button or link elements with JavaScript in onclick attributes were added by lower-privilege users

The environment is affected if WPBakery Page Builder version is below 7.6 AND untrusted users with contributor-level access exist on the site, or if compromised content with malicious onclick attributes is present in posts or pages.

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 7.6 or later
Fixed in 7.6
Interim mitigation

Update WPBakery page builder to version 7.6 or later. Until patched, limit user registration to trusted roles only and consider implementing Content Security Policy headers to mitigate XSS execution.

Recommended fix High confidence

WPBakery Page Builder version 7.6 or later

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Log in to WordPress admin dashboard
  3. 3. Navigate to Plugins > Installed Plugins
  4. 4. Locate 'WPBakery Page Builder' (also known as Visual Composer) in the plugin list
  5. 5. If an update is available, click 'Update Now' to upgrade to version 7.6 or later
  6. 6. After updating, verify the plugin version shows 7.6 or higher under Plugins > Installed Plugins
  7. 7. Clear any caching plugins or server-side caches
  8. 8. Test that the button element functionality works correctly on pages using the plugin

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

Fix this in Page Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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