dbcve.org
Page BuilderWordPress extension · Wpbakery

CVE-2025-11160

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-15
Fix available
A fix is available. Upgrade to 8.7 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 Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Custom JS module in all versions up to, and including, 8.6.1. This is due to insufficient input sanitization and output escaping of user-supplied JavaScript code in the Custom JS module. This makes it possible for authenticated attackers with contributor-level access or higher to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page via the WPBakery Page Builder Custom JS module granted they have access to the WPBakery editor for post types.

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 contains a stored XSS vulnerability in its Custom JS module (versions up to 8.6.1). Due to insufficient input sanitization and output escaping of user-supplied JavaScript code, authenticated attackers with contributor-level or higher access can inject malicious scripts that execute whenever users access pages containing the injected Custom JS.

MitigationUpdate WPBakery Page Builder to version 8.6.2 or later once available, audit all pages using the Custom JS module for malicious entries, and consider restricting editor access to the Custom JS feature.

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:< 8.7

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. Confirm WPBakery Page Builder is installed
    Check your WordPress plugins directory or the WPBakery plugin status in the WordPress admin dashboard under Plugins.
    Affected if WPBakery Page Builder is present and active on the WordPress site.
  2. Identify the installed WPBakery version
    Navigate to WP-Admin > Plugins > WPBakery Page Builder and view the plugin details to see the installed version number.
    Affected if The installed version is below 8.7 (versions 8.6.1 and earlier are vulnerable).
  3. Check if Custom JS module is enabled and in use
    Navigate to WPBakery Page Builder settings or inspect page editor options to determine if the Custom JS feature is accessible. Alternatively, check WordPress post meta tables (typically wp_postmeta) for entries with meta_key containing 'vc_js' or 'custom_js'.
    Affected if The Custom JS module is enabled and there are posts or pages using custom JavaScript.
  4. Inspect Custom JS entries for malicious content
    Review the Custom JS content in the affected pages via the WPBakery editor or by querying the wp_postmeta table for meta_value containing script tags, javascript: URIs, or event handlers (onclick, onerror, onload, etc.).
    Affected if Any Custom JS entries contain unsanitized script tags, event handlers, or suspicious encoded JavaScript that could indicate exploitation.
  5. Verify contributor-level or higher user access exists
    Review WordPress user roles in WP-Admin > Users to confirm accounts with contributor, author, editor, or administrator roles exist, as these roles can access the Custom JS module.
    Affected if Multiple users with contributor-level or higher access exist, increasing the potential attack surface.

A site is affected if WPBakery Page Builder version is below 8.7, the Custom JS module is in use, and there are users with contributor-level or higher permissions.

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

Update WPBakery Page Builder to version 8.6.2 or later once available, audit all pages using the Custom JS module for malicious entries, and consider restricting editor access to the Custom JS feature.

Recommended fix High confidence

WPBakery Page Builder 8.7 or later

  1. Backup your WordPress site before performing any updates
  2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. Find WPBakery Page Builder in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 8.7 or later from the WordPress repository
  5. Verify the update completed successfully by checking the plugin version

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

Fix this in Page Builder Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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