CVE-2026-12995

Custom Field Template <= 2.7.8 - Authenticated (Contributor+) Insecure Direct Object Reference to Arbitrary Media File Deletion via 'file_field' Parameter

2026-09-21 18:42
Dmitrii Ignatyev

Strategic Overview

Status
Patched in 2.8
Affected Plugin
Custom Field Template
Affected Version
<= 2.7.8
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-12995
View all Custom Field Template vulnerabilities

At a glance

CVE-2026-12995 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Custom Field Template WordPress plugin, affecting versions <= 2.7.8. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.8; sites on affected versions should update now. Disclosed September 2026, reported by Dmitrii Ignatyev.

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Custom Field Template <= 2.7.8 takes an account at Contributor level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Custom Field Template the fix is 2.8: builds <= 2.7.8 are affected, anything from 2.8 onward is not.

Remediation

Update to version 2.8, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Custom Field Template 2.8 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-12995https://www.wordfence.com/threat-intel/vulnerabilities/id/02f44f5b-c513-4aba-b895-65df681620c6https://nvd.nist.gov/vuln/detail/CVE-2026-12995

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C