Delete Custom Fields
Approved changes feed: RSS · Atom
cpe:2.3:a:gluten:delete_custom_fields:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Gluten (6750ba4b-670c-55b6-9886-4ade69825319) |
|---|---|
| Product | Delete Custom Fields (48490dbb-a562-58d1-b8e1-5c7487f28762) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-0613 |
vulnerable | 2026-06-08 06:22:01.484478 |
Delete Custom Fields <= 0.3.1 - Cross-Site Request Forgery to Post Meta Deletion
MEDIUM (6.1)
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.
Published: 2024-05-02T16:52:34.387Z
Updated: 2026-04-08T17:19:50.509Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.