Skip to main content
Menu
CVEs

WPBakery Page Builder stored XSS in 'values' shortcode attribute

CVE-2026-122223Published November 21, 2026, updated

6.4MediumCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported

Summary

A stored cross-site scripting flaw in WPBakery Page Builder lets an attacker with contributor-level or higher access inject scripts into pages, which then run for any user who opens the affected page. The attacker can exploit it remotely over the network, through the plugin's 'values' shortcode attribute, and no user action is needed to trigger it.

Written by a model

Original description

The plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'values[text_shadow_color]' parameter in all versions up to, and including, 9.1 due to insufficient input sanitization and output escaping. 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. The wp_kses_post sanitization applied at save time does not strip the payload because it is stored as URL-encoded JSON inside a shortcode attribute, containing no literal HTML tags for kses to tokenize, leaving the malicious value intact until render time.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-122223 (WPBakery Page Builder <= 9.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'values' Shortcode Attribute), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-122223 (entry last updated 2026-11-21):
Affected:
- wpbakery WPBakery Page Builder: through 9.1
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-122223 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-122223 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/100c1fed-e67f-45fd-ac2a-55280944a27c?source=cve
- https://kb.wpbakery.com/docs/release-notes/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-122223
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-122223"}.

Affected versions

cve.now Index

14Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.4/10CVSS 6.4
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active
  • Would score about 33 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkkb.wpbakery.com · docs/release-notes
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-122223
RecordNVD · CVE-2026-122223
Other links 1
Linkwordfence.com · threat-intel/vulnerabilities/id/100c1fed-e67f-45fd-ac2a-55280944a27c?source=cve

Questions about CVE-2026-122223

Is CVE-2026-122223 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: cve.now feed data

Which versions are affected by CVE-2026-122223?

WPBakery Page Builder: through 9.1.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.