LIVE COMPOSER · CVE-2025-15714 · Package
NO FIX YET · SEE WHAT TO DO
The Live Composer WordPress plugin before 2.1.24 does not sanitise or escape some Button module settings before showing them on the front end. An administrator can store script in those settings that runs in other users' browsers, even where unfiltered_html is disabled, such as multisite.
first public Nov 11, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Sites running the Live Composer WordPress plugin before 2.1.24, particularly multisite setups where administrators lack unfiltered_html. Exploitation requires an account with high privileges, so sites with only trusted administrators carry lower risk. Sites without the plugin or already on 2.1.24 or later are not affected.
Not affected if plugin-not-installed, version-2.1.24-or-later
Who cares live-composer, multisite, wordpress
2.1.24.2.1.24 or later.The Live Composer WordPress plugin before 2.1.24 does not sanitise and escape some of its Button module settings before outputting them on the front end, which could allow high-privilege users such as administrators to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (e.g. in multisite setups).
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.