WordPress plugin
Delete Custom Fields security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the plugin or restrict access to the affected feature until the vendor ships a patch.
- Critical0
- High0
- Medium1
- Low0
All Delete Custom Fields vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.1 | Cross-Site Request Forgery to Post Meta Deletion ≤0.3.1No patch available | CVE-2024-0613 |
- Medium6.1Cross-Site Request Forgery to Post Meta Deletion
≤0.3.1No patch available
Delete Custom Fields: common questions
Does Delete Custom Fields have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in Delete Custom Fields: 1 medium. At least one is not fixed in the latest version.
How do I check which version of Delete Custom Fields I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent Delete Custom Fields vulnerability?
CVE-2024-0613, published Apr 15, 2024: Delete Custom Fields <= 0.3.1 - Cross-Site Request Forgery to Post Meta Deletion. Severity: Medium (CVSS 6.1).
Is any Delete Custom Fields vulnerability listed in CISA KEV?
No. None of the known Delete Custom Fields vulnerabilities is currently listed in the CISA KEV catalog.