# CVE-2026-2312: Missing authorization in Media Library Folders

> Authenticated attackers can delete or rename other users' attachments due to missing authorization checks in the Media Library Folders plugin.

- **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:** 14 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-6jhh-8c75-gvr4

## What is CVE-2026-2312?

CVE-2026-2312 is a medium-severity missing authorization vulnerability in maxfoundry Media Library Folders, published on 14 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Media Library Folders plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 8.3.6 via the delete_maxgalleria_media() and maxgalleria_rename_image() functions due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Author-level access and above, to delete or rename attachments owned by other users (including administrators). The rename flow also deletes all postmeta for the target attachment, causing data loss.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-2312 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2312 is a medium-severity missing authorization vulnerability in maxfoundry Media Library Folders, published on 14 Feb 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-2312 in the wild and no public exploit code.

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

## Sources

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

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