WP Cookie Consent ( for GDPR, CCPA & ePrivacy ) <= 3.0.2 - Missing Authorization to Unauthenticated Arbitrary Post Deletion
Strategic Overview
- Status
- Patched in 3.1.0
- Affected Plugin
- WPLP Cookie Consent – Cookie Banner & Consent Management for GDPR, CCPA & Google Consent Mode
- Affected Version
<= 3.0.2- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-3599
At a glance
CVE-2024-3599 is a medium-severity Missing Authorization vulnerability in the WPLP Cookie Consent WordPress plugin, affecting versions <= 3.0.2. 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 3.1.0; sites on affected versions should update now. Disclosed April 2024, reported by Krzysztof Zając.
Vulnerability Overview
The WP Cookie Consent ( for GDPR, CCPA & ePrivacy ) plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the gdpr_policy_process_delete() function in all versions up to, and including, 3.0.2. This makes it possible for unauthenticated attackers to delete arbitrary posts.
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 <= 3.0.2 carries this weakness at gdpr_policy_process_delete(), and reaching it takes no account at all. 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 3.1.0: builds <= 3.0.2 are affected, anything from 3.1.0 onward is not.
Remediation
Update to version 3.1.0, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WPLP Cookie Consent 3.1.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
- 7.5CVE-2025-11754: Cookie Banner Info Exposure
CVE-2025-11754 - 6.3CVE-2022-4974: Freemius SDK <= 2.4.2 Missing Authorization Checks
CVE-2022-4974 - 5.3CVE-2026-82184: WPLP Cookie Consent <= 4.4.1 Missing Authorization
CVE-2026-82184 - 5.3CVE-2025-66080: Cookie Notice for GDPR Missing Authorization
CVE-2025-66080
Other vulnerabilities in WPLP Cookie Consent – Cookie Banner & Consent Management for GDPR, CCPA & Google Consent Mode
- 9.8CVE-2026-75865: WPLP Cookie Consent <= 4.4.1 Arbitrary File Upload
CVE-2026-75865 - 9.8CVE-2026-82970: WPLP Cookie Consent Arbitrary File Upload
CVE-2026-82970 - 7.2CVE-2026-14989: Cookie Banner for GDPR / CCPA <= 4.4.1 Stored XSS
CVE-2026-14989 - 7.2CVE-2026-13360: Cookie Banner for GDPR / CCPA <= 4.3.5 Stored XSS
CVE-2026-13360 - 7.2CVE-2024-4869: WP Cookie Consent Stored XSS
CVE-2024-4869 - 6.4CVE-2026-73359: WPLP Cookie Consent Stored XSS
CVE-2026-73359 - 6.4CVE-2023-23678: WP Cookie Notice for GDPR CSV Injection
CVE-2023-23678 - 5.3CVE-2025-14061: Cookie Banner Unauthenticated Arbitrary Post Deletion
CVE-2025-14061
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C