Live Composer <= 2.1.19 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'dslc_custom_field' Shortcode
Strategic Overview
- Status
- Patched in 2.1.20
- Affected Plugin
- Live Composer – Free WordPress Website Builder
- Affected Version
<= 2.1.19- CVSS
- 6.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2026-16787
At a glance
CVE-2026-16787 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Live Composer WordPress plugin, affecting versions <= 2.1.19. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.1.20; sites on affected versions should update now. Disclosed August 2026, reported by Wordfence PRISM.
Vulnerability Overview
The Live Composer – Free WordPress Website Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'dslc_custom_field' Shortcode in all versions up to, and including, 2.1.19 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Live Composer <= 2.1.19 carries this weakness at dslc_custom_field, and reaching it takes an account at Contributor level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Live Composer the fix is 2.1.20: builds <= 2.1.19 are affected, anything from 2.1.20 onward is not.
Remediation
Update to version 2.1.20, or a newer patched version
How does WordSec protect against this?
An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Live Composer 2.1.20 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
- 6.4CVE-2026-16786: Live Composer <= 2.1.19 Stored Cross-Site Scripting
CVE-2026-16786 - 6.4CVE-2026-16788: Live Composer <= 2.1.19 Stored Cross-Site Scripting
CVE-2026-16788 - 6.4CVE-2026-13203: Live Composer <= 2.1.19 Stored Cross-Site Scripting
CVE-2026-13203 - 6.4CVE-2025-68598: Page Builder: Live Composer <= 2.0.6 Stored XSS
CVE-2025-68598
Other vulnerabilities in Live Composer – Free WordPress Website Builder
- 8.8CVE-2023-52206: Page Builder: Live Composer PHP Object Injection
CVE-2023-52206 - 7.5CVE-2025-14071: Live Composer PHP Object Injection
CVE-2025-14071 - 7.5CVE-2024-35780: Page Builder: Live Composer PHP Object Injection
CVE-2024-35780 - 6.4CVE-2025-13537: Live Composer DOM-Based Stored XSS
CVE-2025-13537 - 6.4CVE-2024-35779: Page Builder: Live Composer <= 1.5.42 Stored XSS
CVE-2024-35779 - 6.4CVE-2024-35768: Page Builder: Live Composer <= 1.5.47 Stored XSS
CVE-2024-35768 - 6.4CVE-2023-52193: Page Builder: Live Composer <= 1.5.23 Stored XSS
CVE-2023-52193 - 6.4CVE-2022-4669: Page Builder: Live Composer <= 1.5.22 Stored XSS
CVE-2022-4669
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C