Page BuilderWordPress extension · Wpbakery
CVE-2025-4968
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 WPBakery Page Builder for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via multiple Page Builder elements (Copyright Element, Hover Box, Separator With Text, FAQ, Single Image, Custom Header, Button, Call To Action, Progress Bar, Pie Chart, Round Chart, and Line Chart) in all versions up to, and including, 8.4.1 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 WPBakery Page Builder plugin for WordPress fails to properly sanitize user-supplied attributes and escape output in 12 different elements (including Copyright, Hover Box, Separator With Text, FAQ, Single Image, Custom Header, Button, Call To Action, Progress Bar, Pie Chart, Round Chart, and Line Chart). This allows authenticated users with contributor-level or higher permissions to inject malicious JavaScript that executes in the browsers of anyone accessing the 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
Page BuilderWordPress extension
< 8.5CVSS 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.
-
Confirm WPBakery Page Builder is installedCheck the WordPress plugins directory or view the plugin in WP Admin under Plugins > Installed Plugins. Look for 'WPBakery Page Builder' or 'Visual Composer'.Affected if The plugin is present in the WordPress installation
-
Check installed WPBakery versionIn WP Admin, go to Plugins > Installed Plugins and find the version number listed for WPBakery Page Builder. Alternatively, check the version in the plugin's main PHP file (typically in /wp-content/plugins/js_composer/include/classes/core/access/).Affected if The version number is less than 8.5 (e.g., 8.4.2, 8.4.1, etc.)
-
Identify users with contributor-level or higher accessIn WP Admin, go to Users > All Users and review the role column. Look for users assigned roles of Contributor, Author, Editor, or Administrator.Affected if At least one user exists with Contributor, Author, Editor, or Administrator role
-
Check for use of affected elementsReview pages/posts built with WPBakery. Specifically inspect content using these elements: Copyright, Hover Box, Separator With Text, FAQ, Single Image, Custom Header, Button, Call To Action, Progress Bar, Pie Chart, Round Chart, and Line Chart. Check the page editor (Backend Editor or Frontend Editor) for these element types.Affected if Any of the 12 affected elements are present in published content with user-editable text fields
-
Inspect element settings for unsanitized inputEdit a page containing one of the affected elements. Click on the element to open its settings panel. Examine text fields (such as text, title, caption, content, or custom text fields) for raw HTML or script tags that may have been injected.Affected if Text fields contain unescaped HTML or JavaScript that would execute in a browser
A user is affected if WPBakery Page Builder version is below 8.5 AND contributor-level or higher users exist AND any of the 12 vulnerable elements are in use with user-supplied text that is not properly escaped.
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 · scoped8.5
Update WPBakery Page Builder to version 8.4.2 or later to receive the patch. As a compensating control, implement a Content Security Policy (CSP) to mitigate XSS execution.
Page Builder version 8.5
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate WPBakery Page Builder in the plugin list
- Click 'Update Now' to update the plugin to version 8.5
- After updating, verify the version number shows 8.5
- Test affected elements (Copyright, Hover Box, Separator With Text, FAQ, Single Image, Custom Header, Button, Call To Action, Progress Bar, Pie Chart, Round Chart, and Line Chart) to confirm functionality
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
- Implementation1.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4968 — 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-2025-4968 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