GDPR Cookie Consent <= 2.6.0 - Unauthenticated Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 2.6.1
- Affected Plugin
- GDPR Cookie Consent
- Affected Version
<= 2.6.0- CVSS
- 7.2High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-8397
At a glance
CVE-2024-8397 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the GDPR Cookie Consent WordPress plugin, affecting versions <= 2.6.0. 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 2.6.1; sites on affected versions should update now. Disclosed September 2024, reported by Zitec/Teodora Jilaveanu.
Vulnerability Overview
The GDPR Cookie Consent plugin for WordPress is vulnerable to Stored Cross-Site Scripting via IP headers in all versions up to, and including, 2.6.0 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-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in GDPR Cookie Consent <= 2.6.0 takes no account at all. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For GDPR Cookie Consent the fix is 2.6.1: builds <= 2.6.0 are affected, anything from 2.6.1 onward is not.
Remediation
Update to version 2.6.1, 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: GDPR Cookie Consent 2.6.1 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