# CVE-2026-116044: prasathmani TinyFileManager Remote URL File Upload tinyfilemanager.php unrestricted upload


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-6wpw-wr63-qhp5

## What is CVE-2026-116044?

CVE-2026-116044 is a medium-severity vulnerability in prasathmani TinyFileManager, published on 25 Oct 2026. 

### Official description

A security vulnerability has been detected in prasathmani TinyFileManager up to 2.6. Affected by this issue is some unknown functionality of the file tinyfilemanager.php of the component Remote URL File Upload Module. The manipulation leads to unrestricted upload. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-116044 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116044 is a medium-severity vulnerability in prasathmani TinyFileManager, published on 25 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116044 exists.

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

## Sources

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

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