CVE-2026-54414: error311 FileRise path traversal in shared-folder upload

CVE-2026-54414 · Severity: critical · CVSS 9.8 · Published 2026-06-19

FileRise, a self-hosted file management and storage platform, is vulnerable to a security flaw that allows unauthorized users to overwrite critical system files. By using a specially crafted file upload request, an attacker can bypass security checks to overwrite the administrator account database. This can lead to a complete takeover of the system and, in some cases, allow the attacker to execute malicious code on the server.

Technologies: Error311 FileRise. Vendors: Error311.

Quick answers

Is CVE-2026-54414 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-54414 being exploited in the wild.
How severe is CVE-2026-54414?
Critical severity, with a CVSS score of 9.8, published 19 June 2026.
Which products and versions are affected?
Error311 FileRise before 3.16.0.
Is there a fix for CVE-2026-54414?
A patch was published on 2026-06-17: Version 3.16.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-54414 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-54414?
Check whether you run Error311 FileRise at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A path traversal vulnerability exists in the `/api/folder/uploadToSharedFolder.php` endpoint of FileRise. The `FolderController` validates filenames using `basename()` and a regex that fails to account for URL-encoded characters (e.g., `%2f`). When `UploadModel::handleUpload` subsequently calls `urldecode()`, path separators are re-introduced (e.g., `..%2f` becomes `../`), allowing files to be written outside the intended directory. Because `UploadNamePolicy::isAllowedForWrite()` only checks the final component of the path, the traversal sequence bypasses extension policies. An attacker with a valid shared-folder token can overwrite `users/users.txt` to create an admin account, leading to full application compromise and potential RCE. This is fixed in version 3.16.0 by decoding filenames before validation.

Affected products

  • error311 FileRise before 3.16.0

Timeline

  • 2026-06-17: patched: Version 3.16.0 released
  • 2026-06-19: disclosed: CVE-2026-54414 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.