# CVE-2026-37068: Path traversal in n/a

> A super administrator can overwrite arbitrary PHP files via path traversal in Veno File Manager, leading to remote code execution.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-w63x-8v4m-m3p4

## What is CVE-2026-37068?

CVE-2026-37068 is a high-severity path traversal vulnerability in n/a, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Arbitrary file write in /vfm-admin/index.php?section=translations&action=update in Veno File Manager Project 4.4.9 allows an authenticated user with the role of super administrator to overwrite any php file in the application via a specially crafted POST request to the affected endpoint.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-37068 being exploited?

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

Public exploit code:

- Arbitrary file write in /vfm-admin/index.php?section=translations&action=update in Veno File Manager Project 4.4.9 allows an authenticated user with the role of super administrator to overwrite any php file in the application via a specially crafted POST request to the affected endpoint. (github_poc): https://github.com/jfs-jfs/CVE-2026-37068

## Fix prompt for AI coding agents

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

What it is: CVE-2026-37068 is a high-severity path traversal vulnerability in n/a, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-37068 in the wild and no public exploit code.

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

## Sources

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

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