dbcve.org
Page BuilderWordPress extension · Wpbakery

CVE-2025-7502

MEDIUM · 5.4 CVSS v3.1 Published 2025-08-06
Fix available
A fix is available. Upgrade to 8.6 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 for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via several shortcodes in all versions up to, and including, 8.5 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 confidence

The WPBakery Page Builder plugin for WordPress versions up to 8.5 contains a stored XSS vulnerability in multiple shortcodes due to insufficient input sanitization on user-supplied attributes and inadequate output escaping. Authenticated attackers with contributor-level permissions can inject malicious JavaScript through shortcode attributes that executes when other users view the compromised pages.

MitigationUpdate the WPBakery Page Builder plugin to the latest version beyond 8.5. If no patched version is available, consider using a Web Application Firewall (WAF) or temporarily disabling the plugin until a fix is released.

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.6

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. Check WPBakery Page Builder version
    In WordPress admin, go to Plugins > Installed Plugins and find 'WPBakery Page Builder'. The version number is displayed below the plugin name. Alternatively, check the main plugin file (usually in /wp-content/plugins/js_composer/include/classes/core/class-vc-manager.php or similar) for the 'Version' header comment.
    Affected if The displayed version number is less than 8.6 (for example, 8.5, 8.4, etc.)
  2. Identify WPBakery shortcodes in use
    Review WordPress pages and posts for shortcode usage. WPBakery shortcodes typically appear in post content wrapped in brackets, such as [vc_row], [vc_column], [vc_button], [vc_column_text], or other [vc_*] shortcodes. Use WordPress search or a database query on wp_posts table to find content containing 'vc_' shortcodes.
    Affected if The site uses WPBakery shortcodes and the plugin version is below 8.6, making the stored XSS vulnerability present
  3. Audit user roles with contributor access
    In WordPress admin, go to Users > All Users and review the role column. Look for any users assigned the 'Contributor' role or higher (Editor, Author, Administrator). These roles have the permission level required to create or edit content with shortcodes.
    Affected if Untrusted or external users have contributor-level permissions, which enables them to inject malicious shortcode attributes

Your environment is affected if WPBakery Page Builder is installed at a version below 8.6 and you have content using WPBakery shortcodes, regardless of user role status.

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.6 or later
Fixed in 8.6
Interim mitigation

Update the WPBakery Page Builder plugin to the latest version beyond 8.5. If no patched version is available, consider using a Web Application Firewall (WAF) or temporarily disabling the plugin until a fix is released.

Recommended fix High confidence

WPBakaker Page Builder version 8.6

  1. Backup your WordPress site database and files before proceeding with any updates
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Locate 'WPBakery Page Builder' in the plugin list
  4. Click 'Update now' if an update is available, or manually update to version 8.6
  5. After updating, clear any caching plugins or server-side caches
  6. Test pages using WPBakery shortcodes to ensure functionality is intact
  7. Verify that contributor-level users can no longer inject arbitrary JavaScript through shortcode attributes
Caveat No explicit breaking changes mentioned in the advisory; this appears to be a security-only update

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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