# CVE-2026-5482: Remote Code Execution via Unrestricted File Upload in Responsive FileManager

> Unauthenticated attackers can upload arbitrary files to achieve remote code execution in the unmaintained Responsive FileManager.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-3pvv-gjhm-83qj

## What is CVE-2026-5482?

CVE-2026-5482 is a critical vulnerability in Tecrail Responsive FileManager, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Responsive FileManager's allows an unauthenticated attacker to upload files of any type and extension without restriction using dialog.php endpoint, leading to Remote Code Execution. 

This project is unmaintained at the time of CVE assignment. The vulnerability was found in the latest release 9.14.0

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

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


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

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

## Is CVE-2026-5482 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5482 is a critical vulnerability in Tecrail Responsive FileManager, published on 15 Jun 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-5482 in the wild and no public exploit code.

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

## Sources

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

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