CVE-2025-14071 HIGH

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

Vendor Livecomposer
Product Live Composer – Free WordPress Website Builder
Weakness CWE-502 · Unsafe deserialization
Published December 21, 2025
Last update April 8, 2026

CVSS base score

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

CVSS vector

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

What the vulnerability does

01Description

The Live Composer – Free WordPress Website Builder plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.0.2 via deserialization of untrusted input in the dslc_module_posts_output shortcode. 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 plugin, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.

Explanation of Vulnerability in Simple Terms

02Summary

Live Composer versions up to 2.0.2 contain a deserialization vulnerability that allows authenticated attackers to execute arbitrary PHP code on the site. The vulnerability requires low-level user privileges and high attack complexity, but successful exploitation grants full control over the WordPress installation. Site administrators should update immediately to a version newer than 2.0.2.

What an attacker can do

03Attacker Capabilities

Run arbitrary PHP code on the site and take full control of the WordPress installation.

Potential impact on your site

04Site Impact

Compromised site can be used to steal data, inject malware, or serve malicious content to visitors.

Conditions required to exploit

05Prerequisites

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

Key dates

06Disclosure timeline

December 21, 2025 CVE published
April 8, 2026 Record updated