CVE-2023-4013

GDPR Cookie Compliance <= 4.12.4 - Cross-Site Request Forgery to License Modification

2023-08-07 00:00
Erwan LR

Strategic Overview

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

At a glance

CVE-2023-4013 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the GDPR Cookie Compliance WordPress plugin, affecting versions <= 4.12.4. 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.12.5; sites on affected versions should update now. Disclosed August 2023, reported by Erwan LR.

Vulnerability Overview

The GDPR Cookie Compliance plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.12.4. This is due to missing nonce validation in the /views/moove/admin/settings/licence.php file. This makes it possible for unauthenticated attackers to update and deactivate the plugin's license 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 <= 4.12.4 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 4.12.5: builds <= 4.12.4 are affected, anything from 4.12.5 onward is not.

Remediation

Update to version 4.12.5, 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 4.12.5 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-4013https://www.wordfence.com/threat-intel/vulnerabilities/id/8f847a61-4378-4b04-8eb4-99ef36417b6chttps://nvd.nist.gov/vuln/detail/CVE-2023-4013

Related records

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