Skip to main content
CVE-2025-15714VulnerabilityPublished

The Live Composer WordPress plugin before 2.1.24 does not sanitise and escape some of its Button module settings

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-15714· High

Not known to be exploited : upgrade to 2.1.24 soon.

Data as of 11 Nov 2026, 07:48 UTC

Severity
High

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

  1. Disclosed: evidence found.

    CVE published 11 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 10 Nov 2026.

What to do

Upgrade Live Composer (WordPress plugin) to 2.1.24.

Affected software

ProductAffectedFixed in
Live ComposerAffected
  • <2.1.24
Fixed in
  • 2.1.24

AI-suggested

Update the Live Composer plugin to version 2.1.24 or later, where this vulnerability has been addressed. Since the vulnerability is fixed in 2.1.24, applying this official update is the recommended remediation. No other specific mitigations are indicated.

Description

The Live Composer WordPress plugin versions before 2.1.24 have a vulnerability where some Button module settings are not properly sanitized and escaped before being output on the front end. This flaw allows high-privilege users, such as administrators, to perform stored cross-site scripting (XSS) attacks even if the unfiltered_html capability is disabled, such as in multisite WordPress setups.

References

Community reviews

Loading reviews…