WordPress plugin · Updated daily · Source: Wordfence Intelligence

Live Composer vulnerabilities: affected versions and fixes

Live Composer has 10,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Live Composer at a glance

  • 21 publicly disclosed vulnerabilities, 4 of them rated High or Critical. The most recent was disclosed on Nov 11, 2026.
  • Ranked #2132 by popularity on WordPress.org (10,000+ active installs).
  • The latest version is 2.1.24 (released Nov 6, 2026). The most recent security fix shipped in 2.1.24.
  • 1 vulnerability has no fix yet. Check the list below to see whether it affects how you use the plugin.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Live Composer version

Enter the Live Composer version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “Live Composer”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Live Composer”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (2.1.24). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Live Composer vulnerabilities

  • Live Composer – Free WordPress Website Builder < 2.1.24 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2026-119531

    Affected versions: < 2.1.24

    Fixed in: 2.1.24

    Severity: Medium 6.4 · Disclosed Nov 11, 2026

  • Live Composer – Free WordPress Website Builder < 2.1.24 - Authenticated (Administrator+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2025-15714

    Affected versions: < 2.1.24

    Fixed in: 2.1.24

    Severity: Medium 4.4 · Disclosed Nov 11, 2026

  • Live Composer <= 2.1.22 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2026-119073

    Affected versions: ≤ 2.1.22

    Fixed in: 2.1.23

    Severity: Medium 6.4 · Disclosed Nov 5, 2026

  • Live Composer <= 2.1.22 - Authenticated (Administrator+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2025-15708

    Affected versions: ≤ 2.1.22

    Fixed in: 2.1.23

    Severity: Medium 4.4 · Disclosed Nov 5, 2026

  • Live Composer <= 2.1.21 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'dslc_module_downloads_output' Shortcode Content

    Cross-site scripting (XSS) · CVE-2026-16778

    Affected versions: ≤ 2.1.21

    Fixed in: 2.1.22

    Severity: Medium 6.4 · Disclosed Sep 21, 2026

  • Live Composer <= 2.1.18 - Authenticated (Contributor+) PHP Object Injection via Shortcode

    PHP object injection · CVE-2026-16502

    Affected versions: ≤ 2.1.18

    Fixed in: 2.1.19

    Severity: High 8.8 · Disclosed Sep 7, 2026

  • Live Composer <= 2.1.19 - Authenticated (Contributor+) Stored Cross-Site Scripting via dslc_module_testimonials_output Shortcode

    Cross-site scripting (XSS) · CVE-2026-16786

    Affected versions: ≤ 2.1.19

    Fixed in: 2.1.20

    Severity: Medium 6.4 · Disclosed Aug 31, 2026

  • Live Composer <= 2.1.19 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'dslc_custom_field' Shortcode

    Cross-site scripting (XSS) · CVE-2026-16787

    Affected versions: ≤ 2.1.19

    Fixed in: 2.1.20

    Severity: Medium 6.4 · Disclosed Aug 31, 2026

  • Live Composer <= 2.1.19 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'custom_id' Shortcode Attribute

    Cross-site scripting (XSS) · CVE-2026-13203

    Affected versions: ≤ 2.1.19

    Fixed in: 2.1.20

    Severity: Medium 6.4 · Disclosed Aug 31, 2026

  • Live Composer <= 2.1.19 - Authenticated (Contributor+) Stored Cross-Site Scripting via dslc_module_projects_output Shortcode

    Cross-site scripting (XSS) · CVE-2026-16788

    Affected versions: ≤ 2.1.19

    Fixed in: 2.1.20

    Severity: Medium 6.4 · Disclosed Aug 31, 2026

  • Page Builder: Live Composer <= 2.0.6 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2025-68598

    Affected versions: ≤ 2.0.6

    Fixed in: No fix yet

    Severity: Medium 6.4 · Disclosed Dec 22, 2025

  • Live Composer – Free WordPress Website Builder <= 2.0.2 - Authenticated (Contributor+) PHP Object Injection via dslc_module_posts_output Shortcode

    PHP object injection · CVE-2025-14071

    Affected versions: ≤ 2.0.2

    Fixed in: 2.0.3

    Severity: High 7.5 · Disclosed Dec 20, 2025

  • Live Composer – Free WordPress Website Builder <= 2.0.2 - Authenticated (Contributor+) DOM-Based Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2025-13537

    Affected versions: ≤ 2.0.2

    Fixed in: 2.0.3

    Severity: Medium 6.4 · Disclosed Dec 16, 2025

  • Page Builder: Live Composer <= 1.5.42 - Authenticated (Contributor+) PHP Object Injection

    PHP object injection · CVE-2024-35780

    Affected versions: ≤ 1.5.42

    Fixed in: 1.5.43

    Severity: High 7.5 · Disclosed Jun 19, 2024

  • Page Builder: Live Composer <= 1.5.42 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-35779

    Affected versions: ≤ 1.5.42

    Fixed in: 1.5.43

    Severity: Medium 6.4 · Disclosed Jun 19, 2024

  • Page Builder: Live Composer <= 1.5.47 - Authenticated (Author+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2024-35768

    Affected versions: ≤ 1.5.47

    Fixed in: 1.5.48

    Severity: Medium 6.4 · Disclosed Jun 18, 2024

  • Page Builder: Live Composer <= 1.5.38 - Missing Authorization

    Missing authorization · CVE-2024-32957

    Affected versions: ≤ 1.5.38

    Fixed in: 1.5.39

    Severity: Medium 4.3 · Disclosed Apr 23, 2024

  • Page Builder: Live Composer <= 1.5.35 - Cross-Site Request Forgery

    Cross-site request forgery (CSRF) · CVE-2024-31933

    Affected versions: ≤ 1.5.35

    Fixed in: 1.5.36

    Severity: Medium 4.3 · Disclosed Apr 10, 2024

  • Page Builder: Live Composer <= 1.5.25 - Authenticated (Author+) PHP Object Injection

    PHP object injection · CVE-2023-52206

    Affected versions: ≤ 1.5.28

    Fixed in: 1.5.29

    Severity: High 8.8 · Disclosed Jan 3, 2024

  • Page Builder: Live Composer <= 1.5.23 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2023-52193

    Affected versions: ≤ 1.5.23

    Fixed in: 1.5.24

    Severity: Medium 6.4 · Disclosed Jan 3, 2024

  • Page Builder: Live Composer <= 1.5.22 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode

    Cross-site scripting (XSS) · CVE-2022-4669

    Affected versions: ≤ 1.5.22

    Fixed in: 1.5.23

    Severity: Medium 6.4 · Disclosed Jan 24, 2023

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Nov 11, 2026.

Most common weaknesses in Live Composer

Cross-site scripting (XSS)

15 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

PHP object injection

4 issues

Specially crafted data makes the server behave in unintended ways. Combined with the right conditions, it can lead to a full takeover.

Missing authorization

1 issue

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

Frequently asked questions

Is Live Composer safe to use?

Live Composer is a well-known plugin with 10,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (2.1.24) and turn on automatic updates. That said, 1 issue has no fix yet, so check the list below.

How do I find which version of Live Composer my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesLive Composer on WordPress.org