The Live Composer WordPress plugin before 2.1.24 does not escape several attributes of one of its page-builder
Source GCVE Database
Not known to be exploited : upgrade to 2.1.24 soon.
Data as of 11 Nov 2026, 07:33 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 fixed version 2.1.24 of the Live Composer plugin is available that addresses this vulnerability by properly escaping shortcode attributes. Users should upgrade to version 2.1.24 or later to remediate this issue.
Description
The Live Composer WordPress plugin versions before 2.1.24 contain a vulnerability where several attributes of a page-builder shortcode are not properly escaped before being output inside HTML tag attributes. This flaw allows users with Contributor role or higher to store malicious payloads that execute in the browsers of anyone viewing the affected post, including administrators reviewing submissions.