Skip to main content
CVE-2026-120679VulnerabilityPublished

The Redux Framework plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-120679· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium.

Data as of 21 Nov 2026, 11:01 UTC

CVSS 3.1 base score
5.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.15.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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
davidandersonRedux FrameworkAffected
  • <=4.5.17
Fixed in–

AI-suggested

Since the vulnerability requires an administrator action to trigger, limiting administrator interactions with untrusted users and reviewing plugin updates from the vendor is recommended. Monitor the vendor advisory for official patches or updates. Until a fix is available, restrict plugin usage or user privileges where possible.

Description

The Redux Framework plugin for WordPress up to version 4.5.17 is vulnerable to stored cross-site scripting (XSS) via a specific parameter due to insufficient input sanitization and output escaping. Authenticated users with subscriber-level access or higher can inject malicious scripts that execute when other users view the injected content. Exploitation requires an administrator to take an action to trigger the vulnerability, limiting direct attacker control. The vulnerability arises because the sanitization method wp_kses_post() is bypassed by using allowed HTML tags and attributes with encoded event handlers that become active when processed by WordPress's thickbox.js.

References

Community reviews

Loading reviews…