CVE-2026-16786 MEDIUM

CVE-2026-16786: Live Composer <= 2.1.19 - Authenticated (Contributor+) Stored Cross-Site Scripting via dslc_module_testimonials_output Shortcode

Vendor Livecomposer
Product Live Composer – Free WordPress Website Builder
Weakness CWE-79 · XSS
Published September 1, 2026
Last update September 1, 2026

CVSS base score

6.4/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

The Live Composer – Free WordPress Website Builder 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 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. The injected payload survives save-time wp_kses_post filtering because KSES treats shortcode delimiters as opaque, and the unescaped fields — including main_heading_title, view_all_link, main_heading_link_title, and main_filter_title_all — are only rendered when do_shortcode() executes at page-view time.

Explanation of Vulnerability in Simple Terms

02Summary

Live Composer contains a stored cross-site scripting (XSS) vulnerability in versions up to 2.1.19. An authenticated user with low privileges can inject malicious scripts that execute in the browsers of other site visitors, potentially compromising their sessions or stealing data. The vulnerability affects the site scope, meaning the injected code can impact multiple areas of the WordPress installation.

What an attacker can do

03Attacker Capabilities

Inject malicious JavaScript that runs in other users' browsers when they view affected pages.

Potential impact on your site

04Site Impact

Visitors and admins may have their sessions hijacked, credentials stolen, or be redirected to malicious sites.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege WordPress user account (e.g., contributor or subscriber role).

Key dates

06Disclosure timeline

September 1, 2026 CVE published
September 1, 2026 Record updated

Related vulnerabilities

08Related CVE