Path Traversal in FileRise (CVE-2026-54414)
Summary
Path traversal in FileRise (CVE-2026-54414). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.16.0 or later.
Original description
The description as published by the source.
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 %).
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54414 has been found in FileRise.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade FileRise to 3.16.0 or later.
If unsure, ask your IT team or search "FileRise CVE-2026-54414" on the vendor's site.
CVE-2026-54414 (FileRise) — CWE-22 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.16.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in FileRise.
Check the vendor advisory for the affected versions of FileRise.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 3.16.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'FileRise' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'FileRise' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
FileRiseを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade FileRise to 3.16.0ステージング環境で 3.16.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web github.com