CVE-2026-119165 · Package
NO FIX YET · SEE WHAT TO DO
WPBakery Page Builder for WordPress does not sanitize the display name / nickname field, so a logged-in subscriber can store script code that runs in other visitors' browsers. The script runs when a user opens a page that renders the injected name through a Basic Grid with the Post Author element linked.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running WPBakery Page Builder up to and including 9.0.1 where Basic Grid templates render the Post Author element linked to the author. Attackers need a subscriber-level account, and subscribers need an administrator to have assigned or published a post under their account. Sites that do not use WPBakery Basic Grids with that element are less exposed.
Not affected if auth-required, no-basic-grid-post-author
Who cares page-builder, wordpress, wpbakery
wp plugin get js_composer --field=version if WP-CLI is available.9.0.1 are affected; the sources do not state a fixed version.The WPBakery Page Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'display_name / nickname' parameter in all versions up to, and including, 9.0.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful execution requires that at least one public post attributed to the attacker's account be rendered through a Basic Grid using a Grid Builder template with the Post Author element configured to link to the post author; Author-level users can satisfy this precondition unassisted, while Subscribers depend on an administrator having assigned or published a post under their account.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.