# CVE-2016-20083: WordPress More Fields Plugin 2.1 Cross-Site Request Forgery

> Attackers can trick administrators into modifying custom fields via CSRF, requiring a patched version of the More Fields plugin.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-rrrg-9wf8-2ph2

## What is CVE-2016-20083?

CVE-2016-20083 is a medium-severity vulnerability in henrikmelin More Fields, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WordPress More Fields Plugin 2.1 contains a cross-site request forgery vulnerability that allows attackers to perform unauthorized actions by disabling CSRF token validation. Attackers can craft malicious web pages that trick logged-in administrators into adding or deleting custom fields and boxes on the Write/Edit page via POST and GET requests to the options-general.php endpoint.

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

## Which versions are affected by CVE-2016-20083?


## How do I fix CVE-2016-20083?

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

## Is CVE-2016-20083 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-20083 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-20083 and fix it if it is affected.

What it is: CVE-2016-20083 is a medium-severity vulnerability in henrikmelin More Fields, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-20083 exists.

Affected product: henrikmelin More Fields. 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-2016-20083/ (Markdown: https://insights.sbomify.com/CVE-2016-20083/index.md)
```

## Sources

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

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