CVE-2023-6700

Cookie Information | Free GDPR Consent Solution <= 2.0.22 - Authenticated (Subscriber+) Arbitrary Options Update

2024-01-29 00:00
Lucio Sá

Strategic Overview

Status
Patched in 2.0.23
Affected Version
<= 2.0.22
CVSS
8.8High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-6700
View all Cookie Information | Free GDPR Consent Solution vulnerabilities

At a glance

CVE-2023-6700 is a high-severity Missing Authorization vulnerability in the Cookie Information WordPress plugin, affecting versions <= 2.0.22. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.0.23; sites on affected versions should update now. Disclosed January 2024, reported by Lucio Sá.

Vulnerability Overview

The Cookie Information | Free GDPR Consent Solution plugin for WordPress is vulnerable to arbitrary option updates due to a missing capability check on its AJAX request handler in versions up to, and including, 2.0.22. This makes it possible for authenticated attackers, with subscriber-level access or higher, to edit arbitrary site options which can be used to create administrator accounts.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-862: Missing Authorization

Reaching this weakness in Cookie Information <= 2.0.22 takes an account at Subscriber level or above. 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 Cookie Information the fix is 2.0.23: builds <= 2.0.22 are affected, anything from 2.0.23 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

Related records

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