CVE-2026-15136

Cookie Banner for GDPR / CCPA – WPLP Cookie Consent <= 4.3.7 - Cross-Site Request Forgery via Bulk Action to Delete/Resolve Entries

2026-07-27 16:38
Wordfence PRISM

Strategic Overview

Status
Patched in 4.3.8
Affected Plugin
WPLP Cookie Consent – Cookie Banner & Consent Management for GDPR, CCPA & Google Consent Mode
Affected Version
<= 4.3.7
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2026-15136
View all WPLP Cookie Consent – Cookie Banner & Consent Management for GDPR, CCPA & Google Consent Mode vulnerabilities

At a glance

CVE-2026-15136 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WPLP Cookie Consent WordPress plugin, affecting versions <= 4.3.7. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.3.8; sites on affected versions should update now. Disclosed July 2026, reported by Wordfence PRISM.

Vulnerability Overview

The Cookie Banner for GDPR / CCPA – WPLP Cookie Consent plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.3.7. This is due to missing or incorrect nonce validation on the process_bulk_action function. This makes it possible for unauthenticated attackers to permanently delete or forcibly resolve arbitrary GDPR data request records stored in the wpl_data_req table via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in WPLP Cookie Consent <= 4.3.7 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WPLP Cookie Consent the fix is 4.3.8: builds <= 4.3.7 are affected, anything from 4.3.8 onward is not.

Remediation

Update to version 4.3.8, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WPLP Cookie Consent: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPLP Cookie Consent 4.3.8 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-15136https://www.wordfence.com/threat-intel/vulnerabilities/id/7a54b803-7e30-4964-88f0-d79276e67218https://nvd.nist.gov/vuln/detail/CVE-2026-15136

Related records

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