# CVE-2026-75860: JSON Options <= 0.0.4 - Unauthenticated Arbitrary Options Update

> Unauthenticated attackers can update arbitrary WordPress options to enable registration and assign administrator roles, leading to full site takeover.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-8hgw-w4m4-6hmx

## What is CVE-2026-75860?

CVE-2026-75860 is a critical missing authorization vulnerability in Unknown JSON Options, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The JSON Options WordPress plugin through 0.0.4 does not have any capability check or nonce verification on one of its actions, which runs on every request and is available to unauthenticated users, allowing them to update arbitrary WordPress options. This can be leveraged to enable user registration and set the default role to administrator, leading to privilege escalation and full site takeover.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-75860 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75860 is a critical missing authorization vulnerability in Unknown JSON Options, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-75860 in the wild and no public exploit code.

Affected product: Unknown JSON Options. 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-75860/ (Markdown: https://insights.sbomify.com/CVE-2026-75860/index.md)
```

## Sources

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

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