# CVE-2026-94297: Media Library Organizer 2.0.4 - 2.1.3 - Contributor+ Arbitrary Taxonomy Term Creation

> Contributor-level users can create arbitrary taxonomy terms due to missing capability checks, allowing unauthorized content modification.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-5pq2-mhxv-3hgx

## What is CVE-2026-94297?

CVE-2026-94297 is a low-severity missing authorization vulnerability in Unknown Media Library Organizer, published on 30 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Media Library Organizer  WordPress plugin before 2.1.4 does not verify that the requesting user holds the target taxonomy's management capability before creating a new term, allowing users with contributor-level access and above to create publicly visible terms in any taxonomy registered on the site.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-94297 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94297 is a low-severity missing authorization vulnerability in Unknown Media Library Organizer, published on 30 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-94297 in the wild and no public exploit code.

Affected product: Unknown Media Library Organizer. 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-94297/ (Markdown: https://insights.sbomify.com/CVE-2026-94297/index.md)
```

## Sources

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

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