CVE-2026-16613

GDPR Cookie Compliance <= 5.0.0 - Cross-Site Request Forgery

2026-07-27 00:00
Abdullah Kareem

Strategic Overview

Status
Patched in 5.1.0
Affected Plugin
GDPR Cookie Compliance – Cookie Banner, Cookie Consent, Cookie Notice for CCPA, EU Cookie Law
Affected Version
<= 5.0.0
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2026-16613
View all GDPR Cookie Compliance – Cookie Banner, Cookie Consent, Cookie Notice for CCPA, EU Cookie Law vulnerabilities

At a glance

CVE-2026-16613 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the GDPR Cookie Compliance WordPress plugin, affecting versions <= 5.0.0. 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 5.1.0; sites on affected versions should update now. Disclosed July 2026, reported by Abdullah Kareem.

Vulnerability Overview

The GDPR Cookie Compliance plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 5.0.0. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action 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 GDPR Cookie Compliance <= 5.0.0 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 GDPR Cookie Compliance the fix is 5.1.0: builds <= 5.0.0 are affected, anything from 5.1.0 onward is not.

Remediation

Update to version 5.1.0, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-16613https://www.wordfence.com/threat-intel/vulnerabilities/id/de249879-00b8-49b3-8964-f7ab69ab292fhttps://nvd.nist.gov/vuln/detail/CVE-2026-16613

Related records

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