Live Composer < 2.1.23 - Admin+ Stored XSS via Partner Slug
- Exploited
- No known exploitation
- Fix
- Fixed in 2.1.23
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.1.23.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.16% · 5th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 7/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Live Composer, a WordPress plugin, does not sanitise or escape some of its custom post type slug settings before using them in front-end links, which lets a high-privilege user such as an admin carry out stored cross-site scripting attacks even where the unfiltered_html capability is disallowed, such as in multisite setups.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
The Live Composer WordPress plugin before 2.1.23 does not sanitise and escape some of its custom post type slug settings before using them in front-end links, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in a multisite setup).
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity3.5/10CVSS 3.5
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 26 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.1.23.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Unknown Live Composer
fixed in 2.1.23
Evidence 1
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2025-15708
Is CVE-2025-15708 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2025-15708?
Live Composer: before 2.1.23.Source: cve.now feed data
How do I fix CVE-2025-15708?
Upgrade to a fixed version: 2.1.23.Source: cve.now feed data