dbcve.org
Team Builder For Wpbakery Page BuilderWordPress extension · Webdevocean

CVE-2024-13591

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Team Builder For WPBakery Page Builder(Formerly Visual Composer) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'team-builder-vc' shortcode in all versions up to, and including, 1.0 due to insufficient input sanitization and output escaping on user supplied attributes. 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 Team Builder For WPBakery Page Builder plugin for WordPress is vulnerable to stored XSS via the 'team-builder-vc' shortcode. Authenticated users with contributor-level access can inject arbitrary JavaScript through unsanitized user-supplied attributes that are not properly escaped on output.

MitigationUpdate the plugin to version 1.1 or later which includes proper input sanitization and output escaping. Until patched, restrict contributor-level user permissions or disable the plugin.

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
Team Builder For Wpbakery Page BuilderWordPress extension
Affected:= 1.0

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 plugin installation
    Check your WordPress installation for the presence of the Webdevocean Team Builder For WPBakery Page Builder plugin in the wp-content/plugins directory or via the WordPress admin plugins list.
    Affected if The plugin is installed and active in WordPress.
  2. Identify installed version
    Locate the plugin main file (typically named main.php, index.php, or similar within the plugin folder) and check the version header comment, or check the version displayed in the WordPress admin plugins page.
    Affected if The installed version is exactly 1.0.
  3. Check for contributor-level user accounts
    In the WordPress admin dashboard, navigate to Users > All Users and review the role assigned to each account, or query the wp_usermeta table for users with the 'contributor' role.
    Affected if At least one user account with contributor-level permissions exists on the site.
  4. Detect usage of the vulnerable shortcode
    Search your WordPress database (wp_posts table) for content containing the '[team-builder-vc' shortcode string, or use a plugin to scan posts, pages, and custom post types for this shortcode.
    Affected if Any post, page, or custom post type contains the team-builder-vc shortcode.
  5. Inspect shortcode content for malicious scripts
    Examine the content of posts/pages containing the team-builder-vc shortcode in the database or editor. Look for suspicious attribute values such as onmouseover, onerror, javascript:, or script tags within the shortcode parameters.
    Affected if The shortcode contains unexpected attribute values that may indicate XSS payload injection.

You are affected if the plugin version is 1.0, it is installed and active, and either contributor users exist or the vulnerable shortcode is in use on your site.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.1 or later which includes proper input sanitization and output escaping. Until patched, restrict contributor-level user permissions or disable the plugin.

Fix this in Team Builder For Wpbakery Page Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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