# CVE-2026-114262: file-management-system FileController.php store unrestricted upload


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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:** 21 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-prff-qhhj-5r4c

## What is CVE-2026-114262?

CVE-2026-114262 is a medium-severity vulnerability in file-management-system, published on 21 Oct 2026. 

### Official description

A vulnerability was determined in file-management-system dc9ce1bf27f94b23d906cb1e86ce374dc94ca5df. Impacted is the function store of the file app/Http/Controllers/FileController.php. This manipulation of the argument File causes unrestricted upload. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The project was informed of the problem early through an issue report but has not responded yet.

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

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


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

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

## Is CVE-2026-114262 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114262 is a medium-severity vulnerability in file-management-system, published on 21 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114262 exists.

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

## Sources

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

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