# CVE-2026-12995: Missing authorization in Custom Field Template

> Authenticated contributors can delete arbitrary media files via IDOR in Custom Field Template plugin, causing content loss.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-82h9-w9pg-f542

## What is CVE-2026-12995?

CVE-2026-12995 is a medium-severity missing authorization vulnerability in hiroaki-miyashita Custom Field Template, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-12995?


## How do I fix CVE-2026-12995?

No fix has been published for CVE-2026-12995 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-12995 being exploited?

There is no known exploitation of CVE-2026-12995 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-12995 and fix it if it is affected.

What it is: CVE-2026-12995 is a medium-severity missing authorization vulnerability in hiroaki-miyashita Custom Field Template, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-12995 in the wild and no public exploit code.

Affected product: hiroaki-miyashita Custom Field Template. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-12995/ (Markdown: https://insights.sbomify.com/CVE-2026-12995/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-12995
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-12995
- OSV: https://osv.dev/vulnerability/CVE-2026-12995

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-12995/
Summaries are generated and may contain mistakes; the official description above is the record.