# CVE-2026-82524: UnoPim File Upload RCE via TinyMCE Image Upload Endpoint

> Authenticated administrators can upload arbitrary PHP files via TinyMCE, leading to remote code execution on the server.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-q5p4-3w6j-xg73

## What is CVE-2026-82524?

CVE-2026-82524 is a high-severity vulnerability in unopim, published on 2 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

UnoPim before 2.1.5 contains an authenticated file upload vulnerability that allows authenticated administrators to upload arbitrary PHP files through the TinyMCE image upload endpoint due to missing file extension and MIME type validation. Attackers can upload a PHP web shell to the public storage disk and execute arbitrary operating system commands on the server by accessing the uploaded file at the URL returned in the server response.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2026-82524 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82524 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82524 is a high-severity vulnerability in unopim, published on 2 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82524 exists.

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

## Sources

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

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