VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

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

CVE-2026-12995Published · Updated

Action summary

Affected: ≤2.7.8Update to 2.8 or newer

All remediation steps
Watch plugin
Severity
Medium4.3
CVSS
4.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:L Privileges required
Low
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-639 Authorization Bypass Through User-Controlled Key
Required access
Unknown
Exploit prediction (EPSS)
0.4% chance in 30 days31th percentile
CISA KEV
Not listed
On this page8

Am I affected?

Custom Field Template custom-field-template

  1. Affected≤ 2.7.8
  2. Patched in2.8

Update to 2.8 or newer.

You are affected if you run ≤ 2.7.8. Version 2.8 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Custom Field Template.
  • No admin access? Run a passive check of your site. It reads public files only.

What to do

  1. Update to version 2.8, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Custom Field Template to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Dmitrii Ignatyev.

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Custom Field Template

All 15
More vulnerabilities in Custom Field Template
SeverityVulnerabilityCVEPublished
Medium6.5Authenticated (Contributor+) SQL Injection via 'post_ID' Parameter
≤2.7.8Update to 2.8
CVE-2026-9855
Medium6.5Authenticated (Contributor+) SQL Injection
≤2.7.8Update to 2.8
CVE-2026-57687
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting
≤2.7.7Update to 2.7.8
CVE-2025-68607
Medium4.3Authenticated (Subscriber+) Information Exposure
≤2.7.6Update to 2.7.7
CVE-2025-63058
Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting
≤2.6.5Update to 2.6.6
CVE-2024-44062

Timeline

  1. CVE published

    Severity medium, CVSS 4.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
EPSS
Exploit Prediction Scoring System by FIRST.org.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?