Quick answers
- Is CVE-2025-15714 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-15714 being exploited in the wild.
- How severe is CVE-2025-15714?
- Informational severity, published 11 November 2026.
- Which products and versions are affected?
- Live Composer before 2.1.24.
- Is there a fix for CVE-2025-15714?
- Yes: fixed in 2.1.24. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-15714 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-15714?
- 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.24
Technical details
The plugin does not sanitize and escape Button module settings before output on the front end, allowing stored cross-site scripting (XSS). Attack requires high-privilege administrator access; the vulnerability persists even when the unfiltered_html capability is disabled, making multisite installations vulnerable. An administrator can inject JavaScript that executes for all visitors viewing the affected page.
Affected products
- Live Composer Live Composer before 2.1.24
Timeline
- 2026-11-09: disclosed
- 2026-11-11: advisory