CVE-2026-4068 | Add Custom Fields to Media <= 2.0.3 - Cross-Site Request Forgery to Custom Field Deletion via 'delete' Parameter

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-19 Last update: 2026-04-22 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2026-4068 is rated Low Risk (18.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.13%). Mandatory action: Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-4068

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.01% 0.13% +0.12%
2 2026-03-19 0.01%

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-4068

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 1.4 [email protected]

Weakness enumeration for CVE-2026-4068

Affected software / configurations for CVE-2026-4068

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-4068

URL Tags
https://plugins.trac.wordpress.org/browser/add-custom-fields-to-media/tags/2.0.3/admin/partials/add-custom-fields-to-media-admin-display.php#L38
https://plugins.trac.wordpress.org/browser/add-custom-fields-to-media/tags/2.0.3/admin/partials/add-custom-fields-to-media-admin-display.php#L48
https://plugins.trac.wordpress.org/browser/add-custom-fields-to-media/trunk/admin/partials/add-custom-fields-to-media-admin-display.php#L38
https://plugins.trac.wordpress.org/browser/add-custom-fields-to-media/trunk/admin/partials/add-custom-fields-to-media-admin-display.php#L48
https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3481588%40add-custom-fields-to-media&new=3481588%40add-custom-fields-to-media&sfp_email=&sfph_mail=
https://www.wordfence.com/threat-intel/vulnerabilities/id/259a4950-9377-4d18-86ad-aadd97dcdbc7?source=cve
cvelogic Threat Intelligence