CVE-2026-4068

{"id": "CVE-2026-4068", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "security@wordfence.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 4.3, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "REQUIRED", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 2.8}]}, "published": "2026-03-19T07:16:00.090", "references": [{"url": "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", "source": "security@wordfence.com"}, {"url": "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", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/add-custom-fields-to-media/trunk/admin/partials/add-custom-fields-to-media-admin-display.php#L38", "source": "security@wordfence.com"}, {"url": "https://plugins.trac.wordpress.org/browser/add-custom-fields-to-media/trunk/admin/partials/add-custom-fields-to-media-admin-display.php#L48", "source": "security@wordfence.com"}, {"url": "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=", "source": "security@wordfence.com"}, {"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/259a4950-9377-4d18-86ad-aadd97dcdbc7?source=cve", "source": "security@wordfence.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security@wordfence.com", "description": [{"lang": "en", "value": "CWE-352"}]}], "descriptions": [{"lang": "en", "value": "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."}], "lastModified": "2026-03-19T13:25:00.570", "sourceIdentifier": "security@wordfence.com"}