CVE-2026-12995
MediumCVSS 4.3Summary
The Custom Field Template plugin for WordPress in versions up to and including 2.7.8 is vulnerable to Insecure Direct Object Reference via edit_meta_value due to missing validation on a user-controlled key. An authenticated attacker with contributor-level access or higher can delete arbitrary media attachments site-wide by supplying any numeric attachment ID in the file-field parameter alongside the corresponding delete flag, causing content loss and broken pages.
Risk Assessment
An attacker can delete media files, leading to content loss and broken web pages.
Recommendation
Update the Custom Field Template plugin to a version newer than 2.7.8 as soon as it becomes available.
Other vulnerabilities in Custom Field Template
See all- CVE-2026-9855Medium
The Custom Field Template plugin for WordPress is vulnerable to generic SQL Injection via the 'post_ID' parameter in all versions up to and including 2.7.8 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This allows authenticated attackers with contributor-level access and above to append additional SQL queries into existing ones, potentially extracting sensitive information from the database. The capability check is bypassable because WordPress internally casts $id to an integer for permission evaluation while the full unsanitized string is passed to the SQL sink.
- CVE-2026-57687High
The Custom Field Template plugin for WordPress versions 2.7.8 and earlier contains a Contributor SQL Injection vulnerability. An attacker with contributor privileges can inject malicious SQL queries into the database.
Original NVD description (English source)
The Custom Field Template plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.7.8 via the edit_meta_value due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with contributor-level access and above, to delete arbitrary media attachments site-wide by supplying any numeric attachment ID in the file-field parameter alongside the corresponding delete flag, causing content loss and broken pages. Exploitation requires that the attacker's post is governed by a Custom Field Template containing at least one file-type field with the mediaRemove option not enabled, which is the default configuration for file fields.