dbcve.org
Page BuilderWordPress extension · Wpbakery

CVE-2025-4965

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-19
Fix available
A fix is available. Upgrade to 8.5 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 the plugin's Grid Builder feature 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 author-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 is vulnerable to Stored Cross-Site Scripting (XSS) in its Grid Builder feature. Authenticated attackers with author-level access or higher can inject malicious scripts through unsanitized user-supplied attributes, which then execute when other users access the affected pages.

MitigationUpdate WPBakery Page Builder to version 8.4.2 or later to patch the insufficient input sanitization and output escaping. Review existing Grid Builder content for any injected malicious scripts.

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

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 is installed
    Log into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'WPBakery Page Builder' or 'WPBakery Page Builder (Visual Composer)' in the list of active plugins.
    Affected if The plugin is present and active in the WordPress installation.
  2. Determine the installed WPBakery version
    In the WordPress admin Plugins page, find WPBakery Page Builder and click on the plugin name or view details to display the installed version number. Alternatively, check the version defined in the main plugin file (usually vc-core or js_composer include file) via FTP or file manager.
    Affected if The installed version is lower than 8.5 (for example, 8.4.2, 8.4.1, 8.4.0, or any earlier version).
  3. Identify Grid Builder content in posts or pages
    Access WordPress admin and navigate to Pages or Posts. Edit any published or draft content. In the page editor with WPBakery active, look for grid elements in the content area, or search the wp_posts database table for post_content containing vc_row, vc_column, or vc_basic_grid shortcodes that indicate Grid Builder usage.
    Affected if The site contains pages or posts using the WPBakery Grid Builder feature (vc_basic_grid, vc_media_grid, or similar grid shortcodes).
  4. Inspect Grid Builder elements for unsanitized attributes
    Edit a page with Grid Builder content in WPBakery backend editor. Click on grid elements to open element settings. Review all text fields, custom CSS classes, link URLs, and data attributes for any injected script tags or javascript: handlers. Also inspect the page source HTML of published pages to see how these attributes are rendered.
    Affected if Any Grid Builder element contains user-supplied data in attributes like class, link, title, or custom fields that are not properly escaped when rendered in the frontend HTML.

A user is affected if WPBakery Page Builder version lower than 8.5 is installed AND the site contains content using the Grid Builder feature with potentially malicious attributes present in the frontend.

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.5 or later
Fixed in 8.5
Interim mitigation

Update WPBakery Page Builder to version 8.4.2 or later to patch the insufficient input sanitization and output escaping. Review existing Grid Builder content for any injected malicious scripts.

Recommended fix High confidence

WPBakery Page Builder version 8.5

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Find WPBakery Page Builder in the plugin list
  4. 4. Click 'Update now' if an update is available, or manually update to version 8.5 or higher
  5. 5. After updating, verify the version number reflects 8.5 or later
  6. 6. Test the Grid Builder functionality to ensure the update doesn't break existing content

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
  • Implementation1.0 h
  • Testing6.0 h
  • Review / QA3.0 h
13.0 hours of engineering $2,220
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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