Add Custom Fields To Media
Approved changes feed: RSS · Atom
cpe:2.3:a:pattihis:add_custom_fields_to_media:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Pattihis (4a1df3a2-d5c8-5410-834a-bd75a3756adc) |
|---|---|
| Product | Add Custom Fields To Media (61360971-b08a-5316-9e44-eaff8a655ce6) |
| 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-2026-4068 |
vulnerable | 2026-06-08 08:05:12.563456 |
Add Custom Fields to Media <= 2.0.3 - Cross-Site Request Forgery to Custom Field Deletion via 'delete' Parameter
MEDIUM (4.3)
The Add Custom Fields to Media plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0.3. This is due to missing nonce validation on the field deletion functionality in the admin display template. The plugin properly validates a nonce for the 'add field' operation (line 24-36), but the 'delete field' operation (lines 38-49) processes the $_GET['delete'] parameter and calls update_option() without any nonce verification. This makes it possible for unauthenticated attackers to delete arbitrary custom media fields via a forged request, granted they can trick a site administrator into performing an action such as clicking on a link.
Published: 2026-03-19T06:46:13.363Z
Updated: 2026-04-08T16:42:27.727Z Reference links
|
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.