Cookie Notice & Compliance for GDPR / CCPA <= 2.1.1 - Authenticated (Admin+) Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.1.2
- Affected Version
< 2.1.2- CVSS
- 4.8Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2021-24569
At a glance
CVE-2021-24569 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.1.2. It carries a CVSS score of 4.8 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 2.1.2; sites on affected versions should update now. Disclosed August 2021, reported by Asif Nawaz Minhas.
Vulnerability Overview
The WP GDPR plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Button Text setting in versions up to, and including, 2.1.1 due to insufficient input sanitization and output escaping. This makes it possible for Admin+ attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations or installations where unfiltered_html has been disabled.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in Cookie Compliance for WordPress < 2.1.2 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.1.2: builds < 2.1.2 are affected, anything from 2.1.2 onward is not.
Remediation
Update to version 2.1.2, 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.1.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
- 6.4CVE-2025-11186: Cookie Notice & Compliance for GDPR / CCPA Stored XSS
CVE-2025-11186 - 6.4CVE-2025-67554: Cookie Notice & Compliance for GDPR / CCPA Stored XSS
CVE-2025-67554 - 6.4CVE-2023-0823: Cookie Notice & Compliance for GDPR / CCPA Stored XSS
CVE-2023-0823 - 6.4CVE-2023-24400: Cookie Notice & Compliance for GDPR / CCPA Stored XSS
CVE-2023-24400
Other vulnerabilities in Cookie Compliance for WordPress – Cookie Consent, GDPR & CCPA
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C