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

CVE-2024-56015

HIGH · 7.1 CVSS v3.1 Published 2024-12-16
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 John Godley Tidy Up allows Reflected XSS.This issue affects Tidy Up: from n/a through 1.3.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Tidy Up plugin allows attackers to trick authenticated administrators into unknowingly triggering actions that result in Reflected XSS. The lack of anti-CSRF token validation on plugin forms or URLs enables malicious request injection, while insufficient output sanitization leads to reflected cross-site scripting.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all plugin forms and AJAX actions, validate nonce server-side on every state-changing request, and apply proper output escaping to prevent reflected 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 Tidy Up plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'tidy-up' or 'tidyup', or query the wp_options table for the active_plugins entry containing 'tidy-up'
    Affected if The Tidy Up plugin folder exists in the plugins directory or is listed in active site plugins
  2. Determine installed plugin version
    Read the main plugin PHP file header (usually tidy-up.php or index.php inside the plugin folder) to find the 'Version:' field, or check the WordPress plugins admin page for the installed version
    Affected if The installed version falls within a vulnerable range (check against any official advisory release notes for version boundaries)
  3. Check plugin PHP files for missing nonce verification
    Search plugin PHP source files for patterns like 'wp_nonce_field', 'check_admin_referer', 'wp_verify_nonce', or 'nonce' validation. Use grep or a code search tool: grep -r 'nonce' /path/to/wp-content/plugins/tidy-up/
    Affected if Plugin PHP files contain NO nonce validation functions on form handlers or AJAX action handlers that process state-changing requests
  4. Inspect plugin forms and URLs for CSRF token presence
    Examine plugin admin pages in the browser using Developer Tools > Network tab, or review source code for form action URLs and hidden nonce fields. Check if forms include fields like '_wpnonce' or 'security' parameters
    Affected if Plugin forms or URLs used for administrative actions do not include anti-CSRF token parameters
  5. Check for insufficient output escaping in reflected output
    Search plugin PHP files for echo or print statements that output request parameters (like $_GET, $_POST, or $_REQUEST values) without sanitization functions such as esc_html(), esc_attr(), or esc_url()
    Affected if Plugin code outputs user-controlled or request-derived data without proper escaping functions, enabling reflected XSS when combined with the CSRF flaw

A defender is affected if the Tidy Up plugin is installed AND its version lacks anti-CSRF token implementation on plugin forms AND the plugin outputs unsanitized request parameters to pages

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 (anti-CSRF tokens) on all plugin forms and AJAX actions, validate nonce server-side on every state-changing request, and apply proper output escaping to prevent reflected XSS.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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