Page BuilderWordPress extension · Wpbakery
CVE-2024-43953
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in webcodingplace Classic Addons – WPBakery Page Builder classic-addons-wpbakery-page-builder-addons allows Stored XSS.This issue affects Classic Addons – WPBakery Page Builder: from n/a through <= 3.5.
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 confidenceA Stored XSS vulnerability in Classic Addons – WPBakery Page Builder plugin (versions through 3.5) allows attackers to inject malicious JavaScript scripts through unsanitized input that gets stored and executed when other users view affected web pages generated by 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
Page BuilderWordPress extension
<= 3.0CVSS 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.
-
Verify WPBakery Page Builder plugin is installedAccess your WordPress admin panel, navigate to Plugins, and confirm Classic Addons - WPBakery Page Builder is installed and activatedAffected if The plugin is installed and active in WordPress
-
Identify the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find Classic Addons - WPBakery Page Builder, and note the version number displayedAffected if The installed version is 3.5 or lower (or matches the <= 3.0 range provided)
-
Locate pages built with the pluginReview your WordPress pages and posts, checking which ones were created or edited using the WPBakery Page Builder editor interfaceAffected if Any content was created using the WPBakery Page Builder editor
-
Inspect rendered pages for suspicious script injectionsView the source code of pages built with WPBakery Page Builder, searching for unexpected <script> tags, event handlers like onload/onerror, or javascript: URIs in HTML attributesAffected if Unexpected or malicious JavaScript code is present in the page source that was not intentionally added by an administrator
A user is affected if the Classic Addons - WPBakery Page Builder plugin is installed with a version at or below 3.0 (or 3.5) and any web pages created with the plugin contain unauthorized injected scripts in their HTML output.
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.
From vendor dataUpgrade to the latest version of Classic Addons – WPBakery Page Builder plugin which includes proper input sanitization and output encoding to neutralize XSS payloads.
Fix this in Page Builder
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-43953 — 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-43953 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