# CVE-2026-62664: FileRise: Authenticated path traversal in createFolder allows arbitrary directory creation outside the upload root

> Authenticated users can create arbitrary directories outside the upload root via path traversal in the folder creation API.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **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:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-p7vh-cjpm-rmrq

## What is CVE-2026-62664?

CVE-2026-62664 is a medium-severity path traversal vulnerability in error311 FileRise, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.19.0, FileRise validates the complete folderName string but does not reject dot-dot path segments before FolderModel::createFolder() constructs and creates the destination. An authenticated low-privileged user with a valid CSRF token and create or owner permission on the parent can submit traversal segments to POST /api/folder/createFolder.php and create directories outside UPLOAD_DIR wherever the web-server account can write. This issue is fixed in version 3.19.0.

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

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


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

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

## Is CVE-2026-62664 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-62664 is a medium-severity path traversal vulnerability in error311 FileRise, published on 14 Oct 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-62664 in the wild and no public exploit code.

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

## Sources

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

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