The Live Composer WordPress plugin before 2.1.24 does not sanitise and escape some of its module settings before
Source GCVE Database
Not known to be exploited : upgrade to 2.1.24 soon.
Data as of 11 Nov 2026, 07:48 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 2.1.24
Exploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 10 Nov 2026.
What to do
Upgrade Live Composer (WordPress plugin) to 2.1.24.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Live Composer | Affected
| Fixed in
|
AI-suggested
A fix is available in Live Composer version 2.1.24. Users should upgrade to version 2.1.24 or later to remediate this vulnerability. Until patched, restrict administrative access to trusted users only and consider additional security controls to limit the impact of potential XSS attacks.
Description
The Live Composer WordPress plugin versions before 2.1.24 do not properly sanitise and escape certain module settings before outputting them in href attributes. This vulnerability allows high-privilege users, such as administrators, to perform Stored Cross-Site Scripting (XSS) attacks even if the unfiltered_html capability is disabled, for example in multisite WordPress setups.