# CVE-2026-119620: 37954679 cak-filemanagement-system add_logs.php move_uploaded_file 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:** 30 Oct 2026
- **Updated:** 30 Oct 2026
- **Also known as:** GHSA-vf8x-qgg6-w422

## What is CVE-2026-119620?

CVE-2026-119620 is a medium-severity vulnerability in 37954679 cak-filemanagement-system, published on 30 Oct 2026. 

### Official description

A vulnerability was determined in 37954679 cak-filemanagement-system up to 5e6433246475e66462e1fea980688de96a049297. This vulnerability affects the function move_uploaded_file of the file admin/add_logs.php. Executing a manipulation of the argument File can lead to unrestricted upload. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. 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-119620?


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

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

## Is CVE-2026-119620 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119620 is a medium-severity vulnerability in 37954679 cak-filemanagement-system, published on 30 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119620 exists.

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

## Sources

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

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