CVE-2022-3399

Cookie Notice & Compliance for GDPR / CCPA <= 2.4.17.1 - Authenticated (Admin+) Stored Cross-Site Scripting

2024-08-15 00:00
c3p0d4y

Strategic Overview

Status
Patched in 2.4.18
Affected Version
<= 2.4.17.1
CVSS
4.4Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2022-3399
View all Cookie Compliance for WordPress – Cookie Consent, GDPR & CCPA vulnerabilities

At a glance

CVE-2022-3399 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Cookie Compliance for WordPress WordPress plugin, affecting versions <= 2.4.17.1. It carries a CVSS score of 4.4 (reachable over the network). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 2.4.18; sites on affected versions should update now. Disclosed August 2024, reported by c3p0d4y.

Vulnerability Overview

The Cookie Notice & Compliance for GDPR / CCPA plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'cookie_notice_options[refuse_code_head]' parameter in versions up to, and including, 2.4.17.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrative privileges and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the injected /wp-admin/admin.php?page=cookie-notice page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Cookie Compliance for WordPress <= 2.4.17.1 carries this weakness at cookie_notice_options[refuse_code_head], and reaching it takes an account at Admin level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Cookie Compliance for WordPress the fix is 2.4.18: builds <= 2.4.17.1 are affected, anything from 2.4.18 onward is not.

Remediation

Update to version 2.4.18, or a newer patched version

How does WordSec protect against this?

An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Cookie Compliance for WordPress 2.4.18 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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