Is CVE-2025-15711 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-15711 being exploited in the wild.

How severe is CVE-2025-15711?

Informational severity, published 11 November 2026.

Which products and versions are affected?

Live Composer Page Builder before 2.1.24.

Is there a fix for CVE-2025-15711?

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-15711 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2025-15711?

Check whether you run Live Composer Page Builder 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.

CVE-2025-15711: Live Composer WordPress plugin stored XSS in module settings

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

The Live Composer WordPress plugin, a page-building tool for WordPress sites, fails to properly sanitize certain module settings before displaying them in links. An administrator or high-privilege user can inject malicious code that persists in the database and executes when other users view the affected page, potentially compromising site security even in restricted environments like multisite setups.

Vendors: Live Composer.

Quick answers

Is CVE-2025-15711 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-15711 being exploited in the wild.
How severe is CVE-2025-15711?: Informational severity, published 11 November 2026.
Which products and versions are affected?: Live Composer Page Builder before 2.1.24.
Is there a fix for CVE-2025-15711?: 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-15711 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2025-15711?: Check whether you run Live Composer Page Builder 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 fails to sanitize and escape module settings before outputting them in href attributes, enabling stored XSS. This affects high-privilege users (administrator and above) and persists in the database. The vulnerability exists even when the unfiltered_html capability is disabled, typically in WordPress multisite configurations.

Affected products

Live Composer Live Composer Page Builder before 2.1.24

Timeline

2026-11-09: disclosed
2026-11-09: advisory

References

https://wpscan.com/vulnerability/3c296d09-122f-420e-9ab1-81ffdfff88c2/

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.