CVE-2024-0613
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 · uneditedThe Delete Custom Fields plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.3.1. This is due to missing or incorrect nonce validation on the ajax_delete_field() function. This makes it possible for unauthenticated attackers to delete arbitrary post meta data via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 confidenceThe Delete Custom Fields WordPress plugin (versions up to 0.3.1) lacks proper nonce validation on its ajax_delete_field() function. This allows unauthenticated attackers to craft malicious requests that, when triggered by an authenticated administrator (via link clicking), can delete arbitrary post meta data from the database.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify the Delete Custom Fields plugin is installedLog into WordPress admin and go to Plugins > Installed Plugins, or check for the plugin folder in wp-content/plugins/Affected if The plugin appears in the list of installed plugins
-
Determine the installed plugin versionIn WordPress admin plugins list, check the version column next to Delete Custom Fields, or open the plugin's main PHP file and look for the 'Version' header in the plugin comment blockAffected if The version listed is 0.3.1 or lower
-
Confirm the vulnerable ajax_delete_field function existsCheck the plugin PHP files for the function named ajax_delete_field() - this function handles the deletion request without proper nonce verification in vulnerable versionsAffected if The ajax_delete_field function exists and is hooked to WordPress ajax actions (wp_ajax_ or wp_ajax_nopriv_)
-
Verify the nonce check is missing or inadequateExamine the ajax_delete_field function code to see if it performs a proper nonce verification check using wp_verify_nonce or check_admin_referer before processing deletion requestsAffected if The function does not verify a nonce token before allowing post meta deletion, or the nonce check can be bypassed
You are affected if the Delete Custom Fields plugin is installed at version 0.3.1 or below AND the ajax_delete_field function is present without proper nonce validation, allowing unauthenticated requests to delete post meta when triggered by an authenticated admin clicking a malicious link.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the plugin to version 0.3.2 or later which includes proper nonce verification. Until then, avoid clicking untrusted links while logged into WordPress admin.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0613 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-0613 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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