CVE-2026-119165
Deferred Deferred - Pending Action

Stored XSS in WPBakery Page Builder WordPress Plugin

Publication date: 2026-11-07

Last updated on: 2026-11-07

Assigner: Wordfence

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

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-07
Last Modified
2026-11-07
Generated
2026-11-07
AI Q&A
2026-11-07
EPSS Evaluated
N/A
NVD
CVE-2026-119165
EUVD
EUVD-2026-118564

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
wpbakery WPBakery Page Builder From 0 (inc) to 9.0.1 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The WPBakery Page Builder plugin for WordPress has a stored Cross-Site Scripting (XSS) vulnerability due to insufficient input sanitization and output escaping in the 'display_name / nickname' parameter. This affects versions up to and including 9.0.1. Authenticated attackers with subscriber-level access or higher can inject malicious scripts into pages. Execution requires a public post by the attacker rendered via a Basic Grid using a Grid Builder template with the Post Author element configured to link to the post author.

Detection Guidance

Check for vulnerable WPBakery Page Builder versions (up to 9.0.1) by inspecting WordPress plugin files or using commands like 'wp plugin list' in WP-CLI. Review posts with Basic Grid elements configured to link to post authors. Monitor for unauthorized script injections in rendered pages.

Impact Analysis

An attacker could inject malicious scripts into your WordPress site, potentially stealing user sessions, redirecting visitors to harmful sites, or defacing pages. Users with subscriber-level access or higher could exploit this if they have access to publish posts. The impact depends on the site's configuration and whether public posts are rendered in vulnerable templates.

Compliance Impact

This vulnerability could lead to unauthorized code execution, potentially compromising user data. For GDPR, this may result in data breaches requiring notification under Article 33. For HIPAA, it could violate safeguards for protected health information. Compliance risks include fines, reputational damage, and mandatory breach reporting depending on the data exposed.

Mitigation Strategies

Update WPBakery Page Builder to version 9.1 or later immediately. Remove or restrict subscriber-level access if not required. Audit all posts using Basic Grid templates with Post Author elements. Implement input sanitization and output escaping for user-provided data.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-119165. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...