CVE-2025-66080

Cookie Notice for GDPR, CCPA & ePrivacy Consent <= 4.0.3 - Missing Authorization

2025-12-30 00:00
Legion Hunter

Strategic Overview

Status
Patched in 4.0.4
Affected Plugin
WPLP Cookie Consent – Cookie Banner & Consent Management for GDPR, CCPA & Google Consent Mode
Affected Version
<= 4.0.3
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-66080
View all WPLP Cookie Consent – Cookie Banner & Consent Management for GDPR, CCPA & Google Consent Mode vulnerabilities

At a glance

CVE-2025-66080 is a medium-severity Missing Authorization vulnerability in the WPLP Cookie Consent WordPress plugin, affecting versions <= 4.0.3. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.0.4; sites on affected versions should update now. Disclosed December 2025, reported by Legion Hunter.

Vulnerability Overview

The Cookie Notice for GDPR, CCPA & ePrivacy Consent plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the wpl_data_req_process_delete() function in versions up to, and including, 4.0.3. This makes it possible for unauthenticated attackers to delete data.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

WPLP Cookie Consent <= 4.0.3 carries this weakness at wpl_data_req_process_delete(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WPLP Cookie Consent the fix is 4.0.4: builds <= 4.0.3 are affected, anything from 4.0.4 onward is not.

Remediation

Update to version 4.0.4, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WPLP Cookie Consent 4.0.4 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-66080https://www.wordfence.com/threat-intel/vulnerabilities/id/eec21a44-d65c-4090-8b60-32d333c54140https://nvd.nist.gov/vuln/detail/CVE-2025-66080

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C