CVE-2025-15712: Live Composer (WordPress plugin) · Cross-site Scripting
Affects Live Composer (WordPress plugin)Source CVE Database V5
Not known to be exploited : upgrade to 2.1.24 soon.
Data as of 11 Nov 2026, 06: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
Update the Live Composer plugin to version 2.1.24 or later, where the vulnerability is fixed. No other mitigation is required as the issue is resolved in this official patch.
Description
A stored cross-site scripting (XSS) vulnerability exists in the Live Composer WordPress plugin versions before 2.1.24. The flaw arises because certain staff member settings are not properly sanitized or escaped before being output on pages. This allows high-privilege users, such as administrators, to inject malicious scripts even when the unfiltered_html capability is disabled, such as in multisite WordPress setups. The issue is fixed in version 2.1.24.