Ultimate Addons For Wpbakery Page BuilderWordPress extension · Brainstormforce
CVE-2024-5253
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 · uneditedThe Ultimate Addons for WPBakery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's ult_team shortcode in all versions up to, and including, 3.19.20 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 confidenceThe Ultimate Addons for WPBakery plugin fails to properly sanitize and escape user-supplied attributes in the ult_team shortcode, allowing authenticated attackers with contributor-level permissions or higher to inject malicious JavaScript that persists on affected pages.
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
Ultimate Addons For Wpbakery Page BuilderWordPress extension
< 3.19.20.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check the installed version of the Ultimate Addons for WPBakery pluginIn WordPress admin, go to Plugins > Installed Plugins, locate 'Ultimate Addons for WPBakery Page Builder' by Brainstormforce, and note the version number displayedAffected if The installed version is lower than 3.19.20.1
-
Identify usage of the ult_team shortcodeSearch your WordPress database or page content for the shortcode [ult_team] using a plugin search tool, WP-CLI 'wp search-replace', or by manually reviewing pages where the Team widget was added via WPBakeryAffected if The ult_team shortcode is present in any post, page, or widget content on the site
-
Verify user role permissions for contributorsNavigate to Users > All Users in WordPress admin and review which users have the Contributor role or higher (Author, Editor, Administrator)Affected if Any user account with Contributor-level or higher permissions exists on the site, as the vulnerability can be exploited by these authenticated users
-
Inspect page content for injected script tags in team member fieldsView the source HTML of pages containing the ult_team shortcode, or use browser developer tools to inspect team member name, bio, position, and social link fields for unsanitized script tags or event handlersAffected if JavaScript code appears unescaped in any team member attribute visible in the page source
You are affected if your Ultimate Addons for WPBakery plugin version is below 3.19.20.1 AND the ult_team shortcode is in use on your site, regardless of whether malicious code has been injected yet.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.19.20.1
Update the Ultimate Addons for WPBakery plugin to version 3.19.21 or later, which patches the sanitization and escaping issues in the ult_team shortcode.
Ultimate Addons For WPBakery Page Builder version 3.19.20.1
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'Ultimate Addons for WPBakery Page Builder' in the plugin list
- Click 'Update now' if an update is available, or manually upload version 3.19.20.1 or higher
- After updating, verify the ult_team shortcode functions correctly on affected pages
- Clear any page caches to ensure changes are reflected
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ultimate Addons For Wpbakery Page Builder
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5253 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-5253 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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