CVE-2025-15708VulnerabilityPublished 7 Nov 2026

The Live Composer WordPress plugin before 2.1.23 does not sanitise and escape some of its custom post type slug

Source GCVE Database

Compare

Authoritative record:CVE-2025-15708· High

Not known to be exploited : upgrade to 2.1.23 soon.

Data as of 7 Nov 2026, 07:47 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.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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-q2pq-rwvm-qmrr

What to do

Upgrade Live Composer (WordPress plugin) to 2.1.23.

Affected software

Product	Affected	Fixed in
Live Composer	Affected <2.1.23	Fixed in 2.1.23

AI-suggested

Upgrade the Live Composer WordPress plugin to version 2.1.23 or later, where this issue has been fixed. No other mitigations are specified. Since the vulnerability requires high privilege user access, restricting administrative access and promptly applying the official fix are the primary recommended actions.

Description

The Live Composer WordPress plugin versions before 2.1.23 contain a vulnerability where certain custom post type slug settings are not properly sanitized and escaped before being used in front-end links. 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.

Impact

An attacker with high privileges on a WordPress site using affected versions of the Live Composer plugin can inject malicious JavaScript code via custom post type slug settings. This stored XSS can lead to session hijacking, privilege escalation, or other malicious actions executed in the context of users visiting affected front-end pages. The vulnerability bypasses the typical unfiltered_html capability restriction, increasing the risk in multisite configurations.

Summary

The Live Composer WordPress plugin prior to version 2.1.23 fails to sanitize and escape some custom post type slug settings before incorporating them into front-end URLs. This improper handling enables users with high privileges (e.g., admins) to inject malicious scripts that are stored and executed in the context of the site, constituting a stored XSS vulnerability. Notably, this attack vector remains viable even when the unfiltered_html capability is disallowed, which is a common restriction in multisite environments.

References

Community reviews

Loading reviews…