dbcve.org
Wp Cookie ConsentWordPress extension · Wpeka

CVE-2024-4869

MEDIUM · 6.1 CVSS v3.1 Published 2024-06-26
Fix available
A fix is available. Upgrade to 3.3.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The WP Cookie Consent ( for GDPR, CCPA & ePrivacy ) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘Client-IP’ header in all versions up to, and including, 3.2.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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WP Cookie Consent plugin for WordPress versions up to 3.2.0 fails to sanitize the Client-IP HTTP header before storing it, and fails to escape the value when outputting it. This allows unauthenticated attackers to inject malicious JavaScript via the Client-IP header. The script executes in the browsers of any user viewing pages where the injected data is displayed, achieving persistent XSS without authentication.

MitigationUpdate the WP Cookie Consent plugin to version 3.2.1 or later which includes proper sanitization of the Client-IP header and output escaping. If immediate update is not possible, consider restricting access to the affected endpoint or deploying a WAF rule to filter Client-IP header injection attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp Cookie ConsentWordPress extension
Affected:< 3.3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WP Cookie Consent plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'WP Cookie Consent' or 'Wpeka Wp Cookie Consent' in the list
    Affected if Plugin is present in the plugins list
  2. Check installed plugin version
    Click on the plugin name in the WordPress plugins list to view details, or inspect the main plugin file (wp-content/plugins/wp-cookie-consent/cookie-consent.php) and look for the 'Version:' header in the plugin comments
    Affected if Version is displayed as 3.2.0 or lower, or the version line in the plugin file shows a number less than 3.3.0
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the plugin has an 'Active' status indicator under the WP Cookie Consent plugin
    Affected if Plugin is currently active
  4. Inspect stored Client-IP values in database
    Access the WordPress database (via phpMyAdmin or wp-cli) and query the options table: SELECT * FROM wp_options WHERE option_name LIKE '%cookie%'; Also check for any custom tables created by the plugin. Look for option values containing script tags, javascript:, or unusual HTML attributes
    Affected if Database contains stored Client-IP values with unescaped HTML or JavaScript content
  5. Check server access logs for Client-IP header manipulation
    Review web server access logs (Apache/nginx) for requests to the WordPress site that include a Client-IP header with suspicious patterns (script tags, event handlers, etc.). Look for entries where the Client-IP header value differs from the source IP
    Affected if Logs show Client-IP headers containing XSS payloads or unusual HTML/JavaScript patterns

If the WP Cookie Consent plugin version is 3.2.0 or lower AND the plugin is active, the environment is vulnerable to CVE-2024-4869 and should be investigated for signs of exploitation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.3.0 or later
Fixed in 3.3.0
Interim mitigation

Update the WP Cookie Consent plugin to version 3.2.1 or later which includes proper sanitization of the Client-IP header and output escaping. If immediate update is not possible, consider restricting access to the affected endpoint or deploying a WAF rule to filter Client-IP header injection attempts.

Recommended fix High confidence

3.3.0

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the WP Cookie Consent plugin and update to version 3.3.0 or later
  4. Verify the plugin updated successfully by checking the installed version number

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wp Cookie Consent Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-4869 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-4869 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data