Quick answers
- Is CVE-2025-15708 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-15708 being exploited in the wild.
- How severe is CVE-2025-15708?
- Informational severity, published 7 November 2026.
- Which products and versions are affected?
- Live Composer before 2.1.23.
- Is there a fix for CVE-2025-15708?
- Yes: fixed in 2.1.23. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-15708 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-15708?
- Check whether you run Live Composer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.1.23
Technical details
The plugin fails to properly sanitize and escape custom post type slug configuration values before rendering them in front-end links, enabling stored XSS injection by high-privilege users. This is particularly dangerous in multisite environments where the unfiltered_html capability is restricted, as attackers with admin role can bypass intent-based mitigations. The vulnerability requires admin-level access to exploit but persists in the database, affecting all site visitors.
Affected products
- Live Composer Live Composer before 2.1.23
Timeline
- 2026-11-05: disclosed
- 2026-11-05: patched: Fixed in version 2.1.23