CVE-2026-4068: CWE-352 Cross-Site Request Forgery (CSRF) in pattihis Add Custom Fields to Media
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.
AI Analysis
Technical Summary
CVE-2026-4068 is a CSRF vulnerability in the Add Custom Fields to Media WordPress plugin (versions up to 2.0.3). The issue arises because the plugin fails to validate a nonce token on the 'delete field' operation, which processes the $_GET['delete'] parameter and calls update_option() without verifying the request's authenticity. This allows unauthenticated attackers to perform unauthorized deletions of custom media fields if they can trick an administrator into clicking a malicious link. The 'add field' operation is properly protected by nonce validation, isolating the vulnerability to the deletion functionality.
Potential Impact
Exploitation of this vulnerability allows an attacker to delete arbitrary custom media fields without authentication by leveraging a CSRF attack against an administrator. This results in integrity loss of the affected WordPress site's custom media field data. There is no direct impact on confidentiality or availability reported. No known exploits are currently observed in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, administrators should avoid clicking on suspicious links and consider disabling or replacing the plugin if possible. Implementing manual nonce validation for the delete operation or applying custom CSRF protections can mitigate the risk. Monitor official vendor channels for updates or patches addressing this vulnerability.
CVE-2026-4068: CWE-352 Cross-Site Request Forgery (CSRF) in pattihis Add Custom Fields to Media
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-4068 is a CSRF vulnerability in the Add Custom Fields to Media WordPress plugin (versions up to 2.0.3). The issue arises because the plugin fails to validate a nonce token on the 'delete field' operation, which processes the $_GET['delete'] parameter and calls update_option() without verifying the request's authenticity. This allows unauthenticated attackers to perform unauthorized deletions of custom media fields if they can trick an administrator into clicking a malicious link. The 'add field' operation is properly protected by nonce validation, isolating the vulnerability to the deletion functionality.
Potential Impact
Exploitation of this vulnerability allows an attacker to delete arbitrary custom media fields without authentication by leveraging a CSRF attack against an administrator. This results in integrity loss of the affected WordPress site's custom media field data. There is no direct impact on confidentiality or availability reported. No known exploits are currently observed in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, administrators should avoid clicking on suspicious links and consider disabling or replacing the plugin if possible. Implementing manual nonce validation for the delete operation or applying custom CSRF protections can mitigate the risk. Monitor official vendor channels for updates or patches addressing this vulnerability.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-03-12T19:38:07.679Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69bba122e32a4fbe5f9bab7f
Added to database: 3/19/2026, 7:09:22 AM
Last enriched: 4/9/2026, 10:08:56 PM
Last updated: 5/2/2026, 4:37:28 PM
Views: 65
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.