# CVE-2026-65054: MediaCMS Private Media Metadata Disclosure via Playlist Ownership Loophole

> Authenticated users can expose private media metadata of other users by adding arbitrary media tokens to their own playlists without proper ownership validation.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-363p-gjpv-2pxq

## What is CVE-2026-65054?

CVE-2026-65054 is a high-severity missing authorization vulnerability in MediaCMS, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MediaCMS 8.2.0 contains an information disclosure vulnerability that allows authenticated users to expose private media metadata belonging to other users by adding arbitrary media tokens to their own playlist without access control checks. Attackers can issue a PUT request to the playlist API endpoint with a known media token to bypass state and ownership validation, then retrieve the playlist to read private media fields including title, description, view count, like count, file size, author username, and encoding status through the unfiltered playlist owner branch in the playlist detail view.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-65054 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-65054 is a high-severity missing authorization vulnerability in MediaCMS, published on 21 Jul 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-65054 in the wild and no public exploit code.

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

## Sources

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

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