# CVE-2026-120429: Camaleon CMS before 2.9.2 Missing Authorization via Admin::MediaController


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 2 Nov 2026
- **Also known as:** GHSA-w2c5-xppr-2hh6

## What is CVE-2026-120429?

CVE-2026-120429 is a high-severity vulnerability in owen2345 Camaleon CMS, published on 2 Nov 2026. 

### Official description

Camaleon CMS before 2.9.2 contains a missing authorization vulnerability in Admin::MediaController that allows low-privileged authenticated users to bypass the role-based Media permission. Attackers can POST to /admin/media/upload to store files, read private media via download_private_file, and use crop with saved_avatar to change other users' avatars.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-120429 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120429 is a high-severity vulnerability in owen2345 Camaleon CMS, published on 2 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120429 in the wild and no public exploit code.

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

## Sources

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

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