CVE-2026-12995 json
Custom Field Template <= 2.7.8 - Authenticated (Contributor+) Insecure Direct Object Reference to Arbitrary Media File Deletion via 'file_field' Parameter
published last mo. modified last mo. also EUVD-2026-84297
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 31%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-12995 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
Affected products
- hiroaki-miyashita Custom Field Template
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/02f44f5b-c513-4aba-b895-65df681620c6?source=cve
- plugins.trac.wordpress.org /browser/custom-field-template/tags/2.7.8/custom-field-template.php#L3500
- plugins.trac.wordpress.org /browser/custom-field-template/tags/2.7.8/custom-field-template.php#L3462
- plugins.trac.wordpress.org /browser/custom-field-template/tags/2.7.8/custom-field-template.php#L105
- plugins.trac.wordpress.org /browser/custom-field-template/tags/2.7.7/custom-field-template.php#L3500
- plugins.trac.wordpress.org /browser/custom-field-template/tags/2.7.7/custom-field-template.php#L3462
- plugins.trac.wordpress.org /browser/custom-field-template/tags/2.7.7/custom-field-template.php#L105
- plugins.trac.wordpress.org /changeset?reponame=&old=3589466%40custom-field-template&new=3589466%40custom-field-template
Sources
- CVE List CVE-2026-12995
- NVD CVE-2026-12995
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.