CVE-2026-4068 Add Custom Fields to Media <= 2.0.3 - Cross-Site Request Forgery to Custom Field Deletion via 'delete' Parameter
Attackers can trick administrators into deleting custom media fields via CSRF due to missing nonce validation in the Add Custom Fields to Media plugin.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-4068?
CVE-2026-4068 is a medium-severity vulnerability in pattihis Add Custom Fields to Media, published on 19 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
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.
Weakness: CWE-352
Which versions are affected by CVE-2026-4068?
How do I fix CVE-2026-4068?
No fix has been published for CVE-2026-4068 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-4068 being exploited?
There is no known exploitation of CVE-2026-4068 in the wild and no public exploit code.
Sources
Also known as GHSA-v95j-rfx2-j67m.