# CVE-2026-114261: MomoTommy file-management-system Files API FileController.php destroy missing authentication


- **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-7fw2-7p48-vj59

## What is CVE-2026-114261?

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

### Official description

A vulnerability was found in MomoTommy file-management-system dc9ce1bf27f94b23d906cb1e86ce374dc94ca5df. This issue affects the function index/store/update/destroy of the file app/Http/Controllers/FileController.php of the component Files API. The manipulation of the argument Request results in missing authentication. The attack can be launched remotely. The exploit has been made public and could be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-114261 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114261 is a medium-severity vulnerability in MomoTommy 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-114261 exists.

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

## Sources

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

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