We’re actively acquiring WordPress agencies. Sell your WordPress business to Freshy.
Let’s discuss

Live Composer – Free WordPress Website Builder Vulnerability (CVE-2026-16786)

Nick Paliughi
On this page

Security Alert Summary

The Live Composer – Free WordPress Website Builder plugin contains a stored cross-site scripting (XSS) vulnerability in the testimonials shortcode output. Authenticated users with contributor-level access or higher can inject scripts into certain shortcode fields that are not escaped at render time, causing the payload to execute when a page containing the injected shortcode is viewed.

CVE Details

  • CVE ID: CVE-2026-16786
  • Affected component: Live Composer – Free WordPress Website Builder plugin for WordPress (testimonials shortcode)
  • Affected versions: all versions up to, and including, 2.1.19
  • Published: September 1, 2026 at 10:17 AM UTC
  • Last modified: September 1, 2026 at 4:16 PM UTC
  • CVSS v3.1: Base Score 6.4, Medium — Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
  • Authentication / privileges / user interaction: Authentication required. Privileges required: Low (authenticated users with contributor-level access or higher). User interaction: None.
  • Primary impact: Confidentiality: Low; Integrity: Low; Availability: None.
  • Weakness (CWE): CWE-79 (Improper Neutralization of Input During Web Page Generation)

Technical Details

This vulnerability is a stored cross-site scripting (XSS) issue in the plugin’s testimonials output shortcode (dslc_module_testimonials_output). Insufficient input sanitization and missing output escaping allow an authenticated attacker (contributor-level or higher) to inject arbitrary script content into shortcode fields. The affected fields named in the report include main_heading_title, view_all_link, main_heading_link_title, and main_filter_title_all.

The injected content can survive the save-time wp_kses_post filtering because KSES treats shortcode delimiters as opaque. The unescaped values are only processed and rendered when do_shortcode() runs at page-view time, which is when the malicious script executes in the context of a visitor or authenticated user viewing the page.

Impact is limited to the effects typical of stored XSS: execution of attacker-supplied script within the victim’s browser context on pages that render the injected shortcode. The report does not indicate exploitation of server-side code execution or availability degradation.

How This Could Impact Your Website

Consider a site where the site owner manages content, internal staff create pages, and external contractors or contributors add content via contributor-level accounts. A contributor could add a malicious payload into a testimonials shortcode field when editing or creating content. When staff or site visitors view the affected page, the injected script runs in their browsers.

  • Internal user data visible in the page context could be read by the script, increasing the risk of exposure of internal email addresses or other page-visible information.
  • Attackers could use the access to craft more convincing targeted phishing or social engineering attacks against staff or contributors by harvesting displayable information.
  • The vulnerability does not, per the provided data, imply full site takeover or availability impact, but it can erode trust and lead to credential or information exposure at the browser level.

If youre unsure whether your site is affected or how to assess your current user roles and plugins, it may be worth having a professional review of your setup.

Recommended Actions

  • Update the affected plugin as soon as a patched version is available.
  • Review and reduce unnecessary user roles, especially contributor-level accounts that can create content with shortcodes.
  • Enforce strong passwords and two-factor authentication for editors and administrators.
  • Remove unused or unmaintained plugins to reduce your attack surface.
  • Monitor site activity and content changes for unusual behavior, including unexpected shortcode content or new testimonial entries.

If youd like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.

References

Nick Paliughihttps://freshysites.com/team/nick-paliughi/
Nick was born in California and now resides in Lake Worth, FL. He has 10 years of experience building and maintaining sites in WordPress, which he is excited to put to use at Freshy. Prior to starting at Freshy in 2022 his focus was on WordPress security & malware removal. When he’s not tending to your website, Nick is installing exhibitions at art galleries and museums in Palm Beach County, and if he’s lucky surfing at the Lake Worth pier.

See our featured website design work

Check out some of the beautiful websites we’ve built for over 2,000 clients.

View projects

We offer WordPress support & maintenance

Shake the stress of ongoing maintenance with plans supported by our team of WordPress experts.

Learn more
Previous Post
WP Recipe Maker Premium Plugin Vulnerability (CVE-2026-7877)
Next Post
Gravity Forms Plugin Vulnerability (CVE-2026-19513)