VulnTitan VulnTitan Security command center
Plugin Vulnerability Hub
Plugin 1 known issue Latest disclosed Apr 15, 2024

Delete Custom Fields Vulnerabilities

Review known vulnerability records for the WordPress plugin Delete Custom Fields (`delete-custom-fields`), including severity, CVE references, affected versions, and patch status.

Recent tracked CVEs on this page include CVE-2024-0613, so operators can jump from disclosure to patch validation without scanning the full feed first.

View on WordPress.org Back to Feed
Known Records
1
High or Critical
0
Patch Coverage
100%
Last Updated
Jul 29, 2024
Related Security Guides

Use these guides while reviewing Delete Custom Fields fixes

Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.

Hardening
WordPress hardening checklist for exposed plugins

Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Plugin Security
WordPress plugin security basics for patch decisions

Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Scanning
WordPress vulnerability scanner buyer's guide

Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Patch Decision Workflow

How to prioritize Delete Custom Fields remediation

Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.

Search-Ready Records
1
1. Match the Package
Confirm the installed WordPress plugin slug is delete-custom-fields before acting on any CVE from this cluster.
2. Sort by Severity
Start with 0 high or critical records, then review medium and unrated findings with public references.
3. Check Patch Evidence
1 record include a patch path; verify compatibility before closing the finding.
4. Monitor Gaps
0 records still lack a listed fixed release, so keep this hub in the review queue.
High-Signal Remediation Targets
CVE-2024-0613 Medium
Cross-Site Request Forgery remediation for Delete Custom Fields

Affected range: Versions up to 0.3.1. Fixed version is not listed yet.

Priority CVE Quick Links

Fast paths into Delete Custom Fields CVE reports

Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.

Indexed CVEs
1
Tracked CVE Issue Type Affected Versions Fixed Version CVSS
CVE-2024-0613
Delete Custom Fields <= 0.3.1 - Cross-Site Request Forgery to Post Meta Deletion
 Cross-Site Request Forgery Versions up to 0.3.1 No patch listed CVSS 6.1
CVE-2024-0613 Medium No patch listed
CVE-2024-0613 Delete Custom Fields Cross-Site Request Forgery

Delete Custom Fields <= 0.3.1 - Cross-Site Request Forgery to Post Meta Deletion

Coverage Snapshot

What this page helps you verify fast

This hub clusters tracked records for Delete Custom Fields so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.

Patch Visibility
1 record include a published patch path, leaving 0 with no listed safe release yet.
Severity Mix
0 critical and 0 high severity findings.
Recent CVEs
CVE-2024-0613
Reference Workflow
Jump from the hub into the full report when you need remediation notes, exploit context, CVSS vectors, or source references.
Triage First

Open the records most likely to drive action

These recent records surface the CVE strings, patch cues, and direct report links most operators need first.

Known Vulnerabilities

Reports for Delete Custom Fields

Sorted by latest disclosure date so newly published issues surface first.

Plugin Medium Patched: No CVE-2024-0613
CVE-2024-0613: Delete Custom Fields <= 0.3.1 - Cross-Site Request Forgery to Post Meta Deletion

The 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...

Published
Apr 15, 2024
Patched Release
Not published
Affected Versions
Versions up to 0.3.1
Next Step
Open the full report for remediation notes and references.
Review CVE-2024-0613 fixed version details Open CVE Reference