# CVE-2026-4068: Add Custom Fields to Media <= 2.0.3 - Cross-Site Request Forgery to Custom Field Deletion via 'delete' Parameter

> Attackers can trick administrators into deleting custom media fields via CSRF due to missing nonce validation in the Add Custom Fields to Media plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Mar 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-v95j-rfx2-j67m

## What is CVE-2026-4068?

CVE-2026-4068 is a medium-severity vulnerability in pattihis Add Custom Fields to Media, published on 19 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Add Custom Fields to Media plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0.3. This is due to missing nonce validation on the field deletion functionality in the admin display template. The plugin properly validates a nonce for the 'add field' operation (line 24-36), but the 'delete field' operation (lines 38-49) processes the $_GET['delete'] parameter and calls update_option() without any nonce verification. This makes it possible for unauthenticated attackers to delete arbitrary custom media fields via a forged request, granted they can trick a site administrator into performing an action such as clicking on a link.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-4068 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4068 is a medium-severity vulnerability in pattihis Add Custom Fields to Media, published on 19 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-4068 in the wild and no public exploit code.

Affected product: pattihis Add Custom Fields to Media. 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-4068/ (Markdown: https://insights.sbomify.com/CVE-2026-4068/index.md)
```

## Sources

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

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