CVE-2025-14044 HIGH

CVE-2025-14044: Visitor Logic Lite <= 1.0.3 - Unauthenticated PHP Object Injection via 'lpblocks' Cookie

Vendor Rodgerholl
Product Visitor Logic Lite
Weakness CWE-502 · Unsafe deserialization
Published December 12, 2025
Last update April 8, 2026

CVSS base score

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

CVSS vector

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

What the vulnerability does

01Description

The Visitor Logic Lite plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.0.3 via deserialization of untrusted input from the `lpblocks` cookie. This is due to the `lp_track()` function passing unsanitized cookie data directly to the `unserialize()` function. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code granted they can access the WordPress site.

Explanation of Vulnerability in Simple Terms

02Summary

Visitor Logic Lite versions 1.0.3 and earlier contain a deserialization vulnerability that allows unauthenticated attackers to execute arbitrary code on the site. The vulnerability requires specific network conditions to exploit but does not require user interaction. An attacker can gain full control of the affected WordPress installation by sending a specially crafted request.

What an attacker can do

03Attacker Capabilities

Run arbitrary code on the site and take full control of it.

Potential impact on your site

04Site Impact

Complete compromise of the site, including data theft, malware injection, and loss of availability.

Conditions required to exploit

05Prerequisites

Network access to the site; no authentication or user interaction required, but exploitation requires specific conditions.

Key dates

06Disclosure timeline

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

Related vulnerabilities

08Related CVE