CVE-2026-16788
MediumCVSS 6.4Exploitation Probability (EPSS)
Low risk26th percentile - higher than 26% of all known CVEs
Summary
The Live Composer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via dslc_module_projects_output Shortcode in all versions up to and including 2.1.19 due to insufficient input sanitization and output escaping. This allows authenticated attackers with contributor-level access and above to inject arbitrary web scripts in pages that execute whenever a user accesses the page.
Risk Assessment
An attacker can inject malicious scripts that execute in visitors' browsers, potentially leading to data theft, session hijacking, or malware distribution.
Recommendation
It is recommended to update the Live Composer plugin to the latest available version that includes security fixes.
Other vulnerabilities in Live Composer
See all- CVE-2026-16502High
The Live Composer – Free WordPress Website Builder plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.1.18 via deserialization of untrusted input. This makes it possible for authenticated attackers with contributor-level access and above to inject a PHP Object. No known POP chain is present in the vulnerable software, meaning no impact unless another plugin or theme with a POP chain is installed. If a POP chain is present, it may allow actions like deleting arbitrary files, retrieving sensitive data, or executing code.
- CVE-2026-16786Medium
The Live Composer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via dslc_module_testimonials_output Shortcode in all versions up to and including 2.1.19 due to insufficient input sanitization and output escaping. This allows authenticated attackers with contributor-level access and above to inject arbitrary web scripts in pages that execute whenever a user accesses the page.
Original NVD description (English source)
The Live Composer – Free WordPress Website Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via dslc_module_projects_output 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. WordPress's shortcode-aware kses handling preserves the serialized shortcode body as a placeholder before content filtering runs, allowing attacker-controlled values such as view_all_link, main_heading_link_title, main_filter_title_all, and button_text to reach render-time sinks entirely unescaped.