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.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
None
No privileges needed
User Interaction
Required
User action required
Impact Assessment
Confidentiality
None
No data leak
Integrity
Low
Partial data modification
Availability
None
No disruption
CVSS Vector v3.1
Weakness Type (CWE)
Vulnerable Products
pattihis:add custom fields to media
References 6
https://plugins.trac.wordpress.org/browser/add-custom-fields-to-media/tags/2.0.…
security@wordfence.com
https://plugins.trac.wordpress.org/browser/add-custom-fields-to-media/tags/2.0.…
security@wordfence.com
https://plugins.trac.wordpress.org/browser/add-custom-fields-to-media/trunk/adm…
security@wordfence.com
https://plugins.trac.wordpress.org/browser/add-custom-fields-to-media/trunk/adm…
security@wordfence.com
https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&ol…
security@wordfence.com
https://www.wordfence.com/threat-intel/vulnerabilities/id/259a4950-9377-4d18-86…
security@wordfence.com