Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as contributor-level user
-
DeliveryCreate/edit post under a CFT with a default file field
-
ExploitSubmit crafted file-field param with victim attachment ID + delete flag
-
ExecutionBypass ownership validation on user-controlled key
-
ImpactPermanently delete arbitrary media site-wide (content loss, broken pages)
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Requires an authenticated account with contributor-level access or above (PR:L). The attacker's post must be governed by a Custom Field Template that contains at least one file-type field whose mediaRemove option is NOT enabled - which is the DEFAULT configuration for file fields, so the precondition is commonly met rather than a rarely-used mode. Exploitation is network-reachable with no user interaction and low complexity: the attacker supplies any numeric attachment ID in the file-field parameter together with the delete flag. Limiting factors: the plugin must be installed and configured with such a template, the attacker must hold a valid low-privilege account, and impact is confined to deletion of media attachments (no data disclosure or code execution). |
| Impact | Moderate, well-bounded risk. The CVSS 4.3 (Medium) vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N correctly captures a network-reachable, low-complexity IDOR (CWE-639) requiring at least contributor-level authentication (PR:L) with no user interaction, and impact limited to integrity (I:L) - arbitrary media-attachment deletion - with no confidentiality (C:N) or formal availability (A:N) rating despite the practical content-loss/broken-page effect. No EPSS score, no CISA KEV listing, and no public exploit are present in the input, so this is no public exploit identified at time of analysis and not confirmed exploited. There is no SSVC decision record supplied. Signals are internally consistent: a Medium-severity, authenticated, destructive-but-not-catastrophic flaw is a routine-patch priority rather than an emergency. Note the input Tag 'Authentication Bypass' conflicts with the actual weakness - this is an authorization/IDOR issue (CWE-639), not an authentication bypass; the CVSS vector itself confirms authentication is REQUIRED (PR:L), so treat the tag as a mislabel, not evidence of pre-auth access. |
| Exploit ScenarioDerived | A contributor-level user (e.g., a self-registered author or a compromised low-privilege account) creates or edits a post governed by a Custom Field Template that includes a default file-type field, then submits the file-field parameter with an arbitrary numeric attachment ID plus the delete flag. Because the handler never validates that the ID belongs to the attacker, the referenced media attachment - anywhere on the site, including images used by admin pages - is permanently deleted, causing broken pages site-wide. No public exploit code is identified, but the plugin source lines are cited in the references, lowering the barrier to reproduction. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 22, 2026
Authenticated users with contributor-level access or above can permanently delete arbitrary media attachments site-wide on any WordPress installation running the Custom Field Template plugin up to and including version 2.7.8, because the edit_meta_value function trusts an attacker-supplied numeric attachment ID in the file-field parameter without verifying ownership. The attack precondition is the plugin's default behavior - a post governed by a template containing at least one file-type field where the mediaRemove option is not enabled - so exposure is common rather than exotic, and exploitation is remote, low-complexity and requires no user interaction. Impact is limited to integrity (deletion of media, causing content loss and broken pages) with no data disclosure or code execution; no public exploit code and no confirmed active exploitation were identified at time of analysis, and a vendor changeset exists although a corrected plugin version could not be independently confirmed.
RemediationAI
No corrected plugin release has been independently confirmed at time of analysis: the description states the flaw affects all versions up to and including 2.7.8, and the references include only a plugin Trac changeset (https://plugins.trac.wordpress.org/changeset?reponame=&old=3589466%40custom-field-template&new=3589466%40custom-field-template), which points to an upstream fix in the development branch but does not establish a tagged, installable patched version - so treat this as upstream fix available (PR/commit) with the released patched version not independently confirmed, and verify the plugin's current release notes or the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/02f44f5b-c513-4aba-b895-65df681620c6?source=cve before deploying. Until a verified fix is applied, the most direct compensating control is to edit every Custom Field Template that contains a file-type field and enable the mediaRemove option, since exploitation depends on that option being disabled; the trade-off is that this changes field behavior for legitimate authors, who may lose the ability to remove attachments the way the site previously allowed. Where that change is unacceptable, restrict contributor-level and above accounts to trusted users, since the vulnerability requires a valid low-privilege login, and audit the user roster for stale or self-registered contributor accounts - this reduces but does not remove risk, as any contributor remains capable of triggering the deletion. Operationally, enable logging and alerting on attachment deletion events, particularly deletions of attachments not owned by the acting user, and maintain tested off-site backups of the uploads directory so that mass media deletion can be recovered; backups mitigate impact but do not prevent the destructive action itself.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This is an Insecure Direct Object Reference (CWE-639, Authorization Bypass Through User-Controlled Key) in the Custom Field Template plugin for WordPress, maintained by Hiroaki Miyashita and tracked under CPE cpe:2.3:a:hiroaki-miyashita:custom_field_template:*:*:*:*:*:*:*:*. WordPress stores post metadata as key/value rows in the postmeta table, and media attachments are themselves posts of type 'attachment' addressed by a numeric ID; the plugin's custom-field handling code (custom-field-template.php, notably around lines 105, 3462 and 3500 in both the 2.7.7 and 2.7.8 tags) processes the file-field and its associated delete flag when saving post meta via edit_meta_value. The root cause is that the routine validates neither the caller's capability over the referenced attachment nor the attachment's association with the post being edited, so any numeric ID placed in the file-field parameter, combined with the delete flag, is passed through to the deletion logic. Because the deletion routine is privileged plugin/site code rather than a core capability check, a low-privileged contributor who cannot normally delete others' media can still reach it. The assessed vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N confirms a network-reachable, low-complexity path requiring a valid low-privilege (contributor) account, with no user interaction and scope unchanged - consistent with an authorization-shaped bug rather than a memory-safety or injection flaw. The trigger condition is the default file-field configuration (mediaRemove option not enabled), which means file-type fields added through the plugin's template UI generally satisfy the precondition without any deliberate misconfiguration by the site owner.
Know when Custom Field Template gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Network-reachable IDOR needing contributor auth (PR:L) and no interaction; deletion damages content integrity (I:L) with no confidentiality and no formal availability rating.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
More in Custom Field Template
View allCross-Site Request Forgery (CSRF) vulnerability in Hiroaki Miyashita Custom Field Template plugin <= 2.5.8 versions. Rat
SQL injection in the Custom Field Template WordPress plugin (versions <= 2.7.8) allows a low-privileged authenticated us
Authenticated SQL injection in the Custom Field Template plugin for WordPress, affecting all versions up to and includin
The Custom Field Template plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's custom fiel
The Custom Field Template plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'cpt' short
Unauth. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low at
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Hiroaki Miy
The Custom Field Template plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all ve
The Custom Field Template plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, an
The Custom Field Template plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and includ
EUVD-2026-84297
GHSA-82h9-w9pg-f542
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB