The Live Composer WordPress plugin before 2.1.23 does not escape a pagination setting supplied through its
Source GCVE Database
Not known to be exploited : upgrade to 2.1.23 soon.
Data as of 7 Nov 2026, 07:36 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.23
Exploitation evidence
Disclosed: evidence found.
CVE published 7 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 6 Nov 2026.
What to do
Upgrade Live Composer (WordPress plugin) to 2.1.23.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Live Composer | Affected
| Fixed in
|
AI-suggested
Update the Live Composer WordPress plugin to version 2.1.23 or later, where this vulnerability has been fixed. No other mitigation is indicated.
Description
The Live Composer WordPress plugin versions before 2.1.23 contain a vulnerability where a pagination setting supplied through post-listing module shortcodes is not properly escaped before being output in an HTML attribute. This flaw allows users with Contributor role or higher to execute Stored Cross-Site Scripting (XSS) attacks.