Add Custom Fields to Media <= 2.0.3 - Cross-Site Request Forgery to Custom Field Deletion via 'delete' Parameter
Strategic Overview
- Status
- Patched in 2.0.4
- Affected Plugin
- Add Custom Fields to Media
- Affected Version
<= 2.0.3- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2026-4068
At a glance
CVE-2026-4068 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Add Custom Fields to Media WordPress plugin, affecting versions <= 2.0.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.0.4; sites on affected versions should update now. Disclosed March 2026, reported by Nabil Irawan.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Add Custom Fields to Media <= 2.0.3 carries this weakness at delete, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Add Custom Fields to Media the fix is 2.0.4: builds <= 2.0.3 are affected, anything from 2.0.4 onward is not.
Remediation
Update to version 2.0.4, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Add Custom Fields to Media: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Add Custom Fields to Media 2.0.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C