CVE-2025-15714 is a Stored Cross-Site Scripting vulnerability in Live Composer before version 2.1.24. The plugin, a drag-and-drop page builder installed on more than 10,000 sites with over 1.6 million all-time downloads, does not sanitize and escape the Button Text setting of its Button module — the name of the button is echoed raw into the page markup. A high-privilege user, an Administrator working in the page builder, can store a payload in the button name that runs in the browser of every visitor who opens the page — up to full administrator account takeover. It matters on WordPress Multisite and on sites with DISALLOW_UNFILTERED_HTML, where administrators are not allowed to post raw HTML. The issue is fixed in 2.1.24.
| CVE | CVE-2025-15714 |
| Plugin Version | Live Composer < 2.1.24, fixed in 2.1.24 |
| All Time | 1 652 332 |
| Active installations | 10 000+ |
| Publicly Published | November 9, 2026 |
| Last Updated | November 11, 2026 |
| Researcher | Krugov Artyom |
| CWE | CWE-79 Cross-Site Scripting |
| PoC | Yes |
| Exploit | No |
| Reference | https://www.cve.org/CVERecord?id=CVE-2025-15714 https://wpscan.com/vulnerability/03a1c844-9a9f-4702-ba6c-3ada3e779014/ |
| Plugin Security Certification by CleanTalk | ![]() |
| Logo of the plugin |
Timeline
| Not recorded | Plugin testing and vulnerability detection in Live Composer were completed; the vulnerability report was sent with the PoC, technical description, and recommendations for remediation. The flaw was found during testing of Live Composer 1.5.52, and the same unescaped output pattern remained in the module up to version 2.1.23. |
| November 6, 2026 | The vendor released version 2.1.24, escaping the link, text, icon, target and inline SVG fields of the Social, Staff, Staff Social, Icon and Button modules to prevent stored XSS via crafted module data. |
| November 9, 2026 | WPScan publicly published the advisory. |
| November 11, 2026 | The CVE record was published in the CVE registry. |
Discovery of the Vulnerability
Live Composer edits pages in its own front-end editor: clicking Edit on a page opens the builder, where the Elements panel lists the available modules. The Button module takes the label of the button — the Button Text field, option button_text — and its output template prints the value back with <?php echo stripslashes( $options['button_text'] ); ?> in modules/button/module.php, with no sanitizing on input and no escaping on output. The module settings are stored together with the page when it is saved in the editor, so whatever is placed in the button name is served to every visitor of that page. Because the value lands directly in the HTML body of the module, the markup it contains is rendered as-is — a persistent (Stored) XSS that needs no attribute breakout at all. In 2.1.24 the vendor wraps the output in esc_html().
Understanding of Stored Cross-Site Scripting attacks
Stored (persistent) Cross-Site Scripting keeps the attacker’s payload on the server so it is served automatically to whoever opens the affected page. This case needs a high-privilege account — the page builder is operated by administrators — which is why the issue is rated Low (CVSS 3.5): on a standard single site an administrator already holds the unfiltered_html capability and can post raw HTML anyway. The risk becomes real on WordPress Multisite and on sites that set DISALLOW_UNFILTERED_HTML, where administrators do not hold it: missing output escaping lets them bypass that restriction and run JavaScript in the context of the site.
The payload does not stay inside the editing screen. The poisoned module is printed on the public front end of the page, so the injected code runs for every visitor — and, most importantly, for every administrator who opens or edits that page in Live Composer, which opens the way to session hijacking and full account takeover.
Exploiting the Stored Cross-Site Scripting Vulnerability
To reproduce the vulnerability on an affected version (below 2.1.24):
- Use a site where administrators cannot post raw HTML: WordPress Multisite, or a single site with
DISALLOW_UNFILTERED_HTMLset totrue. - Log in as an Administrator and open the target page.
- Click Edit to launch the Live Composer front-end editor.
- In Elements, select the Button module and add it to the page.
- Insert the XSS payload into the name of the Button and save the page.
- Open the page on the front end — the stored payload is rendered as page markup and executes for every visitor.
PoC:
POC:
Account - Administrator, on a site where administrators cannot post raw HTML
(WordPress Multisite, or DISALLOW_UNFILTERED_HTML set to true)
1) Open the target page and click Edit to launch the Live Composer front-end editor.
2) In Elements, select the Button module and add it to the page.
3) Insert the payload below into the name of the Button (the Button Text field,
option button_text):
"><script></script><img src=x onerror=alert(document.domain)>
4) Save the page and open it on the front end: the payload is printed as page markup
and the onerror handler executes alert(document.domain) in the browser of every
visitor of the page.
The button name is echoed into the module body without escaping, so the injected markup is rendered as-is: the empty <script></script> shows that arbitrary tags can be planted, and <img src=x onerror=alert(document.domain)> fires as soon as the browser fails to load the non-existent image — no interaction beyond opening the page is needed. In a real attack the harmless alert(document.domain) would be replaced with code that steals the administrator’s session cookie or silently creates a rogue administrator, and it would fire for every visitor, including every administrator who opens or edits the page in Live Composer — stored XSS on behalf of the administrator that ends in account takeover.
Recommendations for Improved Security
To mitigate CVE-2025-15714:
- Update the plugin to version 2.1.24 or later. The 2.1.24 changelog states that the vendor now escapes “the link, text, icon, target and inline SVG fields of the Social, Staff, Staff Social, Icon and Button modules … to prevent stored XSS via crafted module data” — in the Button module specifically, the button text is passed through
esc_html(). - Sanitize module settings on input and escape them on output. A button label is plain text and should always be printed through
esc_html()— never echoed as free-form HTML. - Do not treat the administrator role as a trust boundary for HTML, especially on Multisite and with
DISALLOW_UNFILTERED_HTML. - Review which roles can open pages in the Live Composer editor, and protect those accounts with 2FA.
- Implement a strong Content Security Policy (CSP) to block inline JavaScript execution.
- Deploy a Web Application Firewall to filter XSS payloads before they reach the application.
To prevent this type of attack, follow our methods of XSS prevention.
By addressing Stored XSS vulnerabilities like CVE-2025-15714 early, WordPress site owners and plugin developers can keep public pages — not only admin screens — free of injected scripts. Stay vigilant, stay secure.
#WordPressSecurity #StoredXSS #LiveComposer #WebsiteSafety #StayProtected
Use CleanTalk solutions to improve the security of your website
Krugov Artyom
