Plugins · add-custom-fields-to-media · data as of 2026-11-04
Is Add Custom Fields to Media safe? Known vulnerabilities and latest version
- Latest version
- 2.0.4
- Last updated
- 2026-03-13
- Active installs
- 80+
- Known issues on record
- 1
- Unpatched in latest
- 0
- Tested up to WP
- 6.9.11 · PHP 7.2+
Add custom fields to media uploader and access them in template files. Great for copyrights, image meta etc. — by George Pattichis
What to do
- Update to the latest version (2.0.4). Anything older than 2.0.4 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get add-custom-fields-to-media --field=version shows what you run; wp plugin update add-custom-fields-to-media updates it.
Check your version
Known vulnerabilities
1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 4.3 CVE-2026-4068 · published 2026-03-19
Cross-site request forgery (CSRF) in Add Custom Fields to Media (2.0.3 and older)
- Affected
- 2.0.3 and older
- Fixed in
- 2.0.4 *
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-4068Wordfence advisoryCode change (fix)Plugin source
Recent activity
- 2026-03-13 — latest release on wordpress.org (2.0.4).
- 2026-03-19 — Cross-site request forgery (CSRF) disclosed (CVE-2026-4068), fixed in 2.0.4.
Get an email when Add Custom Fields to Media has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Add Custom Fields to Media (add-custom-fields-to-media) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
- Published this week
- Unpatched in the latest version
- By type of vulnerability
- Plugins by George Pattichis (2 tracked)
Types found in this plugin: Cross-site request forgery (CSRF) (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/add-custom-fields-to-media (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/add-custom-fields-to-media"><img src="https://laskyr.com/plugins/add-custom-fields-to-media/badge.svg" alt="Add Custom Fields to Media vulnerability status"></a>