Delete Custom Fields <= 0.3.1 - Cross-Site Request Forgery to Post Meta Deletion
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| gluten | Delete Custom Fields | unaffected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Wordpress | Wordpress | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-16406 | 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 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. |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.183% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Delete Custom Fields <= 0.3.1 - Cross-Site Request Forgery to Post Meta Deletion | |
| Weaknesses | CWE-352 |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|