Skip to main content
CVE-2026-122223VulnerabilityPublished

The plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'values[text_shadow_color]' parameter in

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-122223· Medium 6.4

Not known to be exploited · CVSS 6.4 Medium.

Data as of 21 Nov 2026, 11:01 UTC

CVSS 3.1 base score
6.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.16.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
wpbakeryWPBakery Page BuilderAffected
  • <=9.1
Fixed in–

AI-suggested

Users should restrict contributor-level access to trusted individuals to reduce risk. Monitor vendor advisories for updates or patches addressing this vulnerability. Since the vulnerability involves insufficient sanitization of a specific parameter, applying custom input validation or output escaping on this parameter may mitigate risk temporarily.

Description

A WordPress plugin is vulnerable to Stored Cross-Site Scripting (XSS) via the 'values[text_shadow_color]' parameter in all versions up to and including 9.1. The vulnerability arises from insufficient input sanitization and output escaping, allowing authenticated users with contributor-level access or higher to inject malicious scripts. The sanitization method used (wp_kses_post) fails to remove the payload because it is stored as URL-encoded JSON inside a shortcode attribute, which bypasses HTML tag-based filtering. This results in script execution when a user views the injected page.

References

Community reviews

Loading reviews…