dbcve.org
Page BuilderWordPress extension · Wpbakery

CVE-2025-10006

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-18
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 plugin's 'rev_slider_vc' shortcode in all versions up to, and including, 8.6 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. This is only exploitable when RevSlider is also installed.

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 the 'rev_slider_vc' shortcode. Attackers with contributor-level access can inject malicious JavaScript through unsanitized shortcode attributes, which then executes when other users view the affected pages. Exploitation requires RevSlider to be installed.

MitigationUpdate the WPBakery Page Builder plugin to the latest version, or implement proper input sanitization and output escaping for the rev_slider_vc shortcode attributes if a patch is unavailable.

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. Verify WPBakery Page Builder version
    Check the installed version of WPBakery Page Builder plugin in WordPress admin under Plugins, or inspect the plugin header in /wp-content/plugins/js_composer/include/classes/core/class-vc-manager.php or the main plugin file
    Affected if version is below 8.7 (e.g., 8.6.x, 8.5.x, etc.)
  2. Confirm RevSlider installation
    Check if the RevSlider (Slider Revolution) plugin is installed and active in WordPress under Plugins, or look for /wp-content/plugins/revslider/ directory
    Affected if RevSlider plugin is present on the site
  3. Detect rev_slider_vc shortcode usage
    Search the WordPress database (wp_posts table) or use a plugin to find instances of the [rev_slider_vc] shortcode in post content, pages, or widgets
    Affected if any content contains the rev_slider_vc shortcode with user-controlled attributes
  4. Review contributor-level access
    Check WordPress user roles under Users > All Users to see if any users have the Contributor role, or inspect role capabilities using a user role editor plugin
    Affected if untrusted users with Contributor-level access exist who can create or edit content containing the shortcode

The environment is affected if WPBakery Page Builder is installed below version 8.7, RevSlider is present, and the rev_slider_vc shortcode is in use where untrusted users could inject malicious attributes.

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 the WPBakery Page Builder plugin to the latest version, or implement proper input sanitization and output escaping for the rev_slider_vc shortcode attributes if a patch is unavailable.

Recommended fix High confidence

8.7 or later

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Find WPBakery Page Builder in the list
  4. If an update is available, click 'Update Now' to upgrade to version 8.7 or later
  5. Alternatively, go to Dashboard > Updates and check for plugin updates
  6. After updating, verify the plugin version is 8.7 or higher in the plugins list
  7. Test that pages using the rev_slider_vc shortcode render correctly

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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-2025-10006 — 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-10006 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