dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-53755

HIGH · 7.1 CVSS v3.1 Published 2024-12-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Cross-Site Request Forgery (CSRF) vulnerability in Andrea Pernici Third Party Cookie Eraser third-party-cookie-eraser allows Stored XSS.This issue affects Third Party Cookie Eraser: from n/a through <= 1.0.2.

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 · moderate confidence

CSRF vulnerability in the Third Party Cookie Eraser WordPress plugin (versions up to 1.0.2) allows attackers to inject malicious scripts via stored XSS. Attackers can craft malicious requests that trick authenticated administrators into triggering the attack, leading to persistent script injection when other users view the affected content.

MitigationImplement WordPress nonces for all form submissions and AJAX actions, and apply proper output escaping when displaying cookie-related data to prevent stored XSS.

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

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
Low

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

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. Identify if Third Party Cookie Eraser plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Third Party Cookie Eraser' in the list of active and inactive plugins.
    Affected if The plugin appears in the installed plugins list, regardless of activation status
  2. Determine installed plugin version
    In the plugins list, click on the plugin name or view the plugin file header (typically in the main PHP file such as third-party-cookie-eraser.php) to read the Version field from the plugin metadata.
    Affected if The version number displayed is 1.0.2 or any version lower than 1.0.2
  3. Inspect plugin for missing nonce validation
    Examine the plugin source code, specifically looking at form handlers and AJAX action callbacks. Search for calls to wp_verify_nonce, check_admin_referer, or wp_nonce_field in files that process user-submitted cookie data.
    Affected if Form processing functions handling cookie-related input do not contain WordPress nonce verification calls, indicating the CSRF protection is missing
  4. Review stored cookie data for injected scripts
    Access the WordPress database (via phpMyAdmin or wp-cli) and query the wp_options table or any custom tables created by the plugin for cookie-related entries. Examine stored values for unescaped HTML script tags, javascript: URIs, or event handler attributes.
    Affected if Database entries related to cookie configuration contain raw HTML script tags or JavaScript code that would execute when rendered in the browser
  5. Check browser console for script execution errors
    As a non-administrator user or in a private/incognito browser window, navigate to pages where the plugin outputs cookie-related content. Open browser developer tools (F12) and check the Console tab for any executed scripts or errors related to injected payloads.
    Affected if The plugin displays cookie-related data on the frontend and malicious scripts execute or appear in the DOM when viewing affected pages

You are affected if the Third Party Cookie Eraser plugin is installed at version 1.0.2 or lower and the plugin lacks CSRF/nonce protection on its form submissions, allowing attackers to inject persistent scripts via authenticated administrator sessions.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement WordPress nonces for all form submissions and AJAX actions, and apply proper output escaping when displaying cookie-related data to prevent stored XSS.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-53755 — 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-53755 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