# CVE-2025-15714: Live Composer WordPress plugin stored XSS in Button module

Source: https://junglewise.ai/threats/cve-2025-15714-the-live-composer-wordpress-plugin-before-2-1-24-does-not  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-11. Updated: 2026-11-11  
License: CC BY 4.0 with a link back

CVE-2025-15714 · Severity: info · Published 2026-11-11

The Live Composer page builder plugin for WordPress fails to properly sanitize settings in its Button module, allowing administrators to inject malicious scripts that execute when the page is viewed. This is particularly dangerous in multisite WordPress installations where administrator accounts are typically restricted from using raw HTML, but can still exploit this vulnerability to bypass those protections and carry out attacks against other users.

Technologies: [Live Composer](https://junglewise.ai/threats/technologies/live-composer-live-composer). Vendors: [Live Composer](https://junglewise.ai/threats/vendors/live-composer).

## 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

## References

- [https://wpscan.com/vulnerability/03a1c844-9a9f-4702-ba6c-3ada3e779014/](https://wpscan.com/vulnerability/03a1c844-9a9f-4702-ba6c-3ada3e779014/)

## Related threats

- [Live Composer WordPress plugin stored XSS in pagination](https://junglewise.ai/threats/cve-2026-119073-the-live-composer-wordpress-plugin-before-2-1-23-does-not-escape)
- [Live Composer WordPress plugin stored XSS via post type slug](https://junglewise.ai/threats/cve-2025-15708-the-live-composer-wordpress-plugin-before-2-1-23-does-not)