CVE-2019-25143

GDPR Cookie Compliance <= 4.0.2 - Missing Authorization

2019-12-27 00:00
Jerome Bruandet

Strategic Overview

Status
Patched in 4.0.3
Affected Plugin
GDPR Cookie Compliance – Cookie Banner, Cookie Consent, Cookie Notice for CCPA, EU Cookie Law
Affected Version
<= 4.0.2
CVSS
5.4Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2019-25143
View all GDPR Cookie Compliance – Cookie Banner, Cookie Consent, Cookie Notice for CCPA, EU Cookie Law vulnerabilities

At a glance

CVE-2019-25143 is a medium-severity Missing Authorization vulnerability in the GDPR Cookie Compliance WordPress plugin, affecting versions <= 4.0.2. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 4.0.3; sites on affected versions should update now. Disclosed December 2019, reported by Jerome Bruandet.

Vulnerability Overview

The GDPR Cookie Compliance plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on the gdpr_cookie_compliance_reset_settings AJAX action in versions up to, and including, 4.0.2. This makes it possible for authenticated attackers to reset all of the settings.

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 interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in GDPR Cookie Compliance <= 4.0.2 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 GDPR Cookie Compliance the fix is 4.0.3: builds <= 4.0.2 are affected, anything from 4.0.3 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2019-25143https://www.wordfence.com/threat-intel/vulnerabilities/id/9116d719-f536-4b8a-9e73-9a8a922f8a35https://nvd.nist.gov/vuln/detail/CVE-2019-25143

Related records

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