CVE-2025-10496

Cookie Notice & Consent <= 1.6.5 - Unauthenticated Stored Cross-Site Scripting

2025-10-08 13:55
Muhammad Yudha - DJ

Strategic Overview

Status
Patched in 1.6.6
Affected Version
<= 1.6.5
CVSS
7.2High
Weakness type
CWE-80 · Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)
CVE
CVE-2025-10496
View all Cookie Notice & Consent vulnerabilities

At a glance

CVE-2025-10496 is a high-severity Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in the Cookie Notice & Consent WordPress plugin, affecting versions <= 1.6.5. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.6.6; sites on affected versions should update now. Disclosed October 2025, reported by Muhammad Yudha - DJ.

Vulnerability Overview

The Cookie Notice & Consent plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the uuid parameter in all versions up to, and including, 1.6.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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

CWE-80: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)

The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as <, >, and & that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages.

Remediation

Update to version 1.6.6, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Cookie Notice & Consent 1.6.6 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

Related records

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