# CVE-2026-54414: FileRise shared-folder upload path traversal allows arbitrary file write and admin takeover

> Attackers can exploit path traversal in FileRise to write arbitrary files and take over administrator accounts.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-jg2q-3m38-6xc2

## What is CVE-2026-54414?

CVE-2026-54414 is a critical path traversal vulnerability in error311 FileRise, published on 19 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FileRise before 3.16.0 is vulnerable to path traversal in the shared-folder upload endpoint (/api/folder/uploadToSharedFolder.php), leading to arbitrary file write and administrator account takeover. The upload filename is validated by FolderController with basename and REGEX_FILE_NAME, which permit URL-encoded sequences (the regex blocks / and \ but not %).

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-54414 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54414 is a critical path traversal vulnerability in error311 FileRise, published on 19 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54414 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-54414/ (Markdown: https://insights.sbomify.com/CVE-2026-54414/index.md)
```

## Sources

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

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