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 %).
Published: 2026-06-19
Score: 9.3 Critical
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

FileRise versions prior to 3.16.0 contain a path traversal flaw in the shared-folder upload endpoint. The filename is validated by basename() and a regex that allows URL-encoded sequences. Because percent-encoding is not normalized before validation, an attacker can supply a filename that, after decoding, includes directory traversal characters. The upload routine copies the file to the target path without containment checks, allowing an attacker to write arbitrary files outside the intended directory. Overwriting a file such as users/users.txt can create an administrator account, leading to unauthenticated administrator takeover.

Affected Systems

FileRise prior to version 3.16.0 is affected. Versions 3.16.0 and later include additional filename validation that rejects percent-encoded traversal sequences, eliminating the flaw.

Risk and Exploitability

CVSS 9.3 indicates critical severity. EPSS 1% indicates low but non-zero probability of exploitation. The flaw is not listed in the CISA KEV catalog. Exploitation requires the ability to send a file to the shared-folder upload endpoint; the vulnerability does not require privileged authentication beyond normal upload capability. Successful exploitation allows arbitrary file writes, which can be used to overwrite system files and create an admin account, giving full control of the application.

Generated by OpenCVE AI on August 10, 2026 at 23:12 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade FileRise to version 3.16.0 or newer to apply the missing validation fix.
  • If an upgrade cannot be performed immediately, disable or restrict the shared-folder upload feature to prevent unauthorized file uploads.
  • Monitor the application for unexpected file modifications, especially in user and admin directories, and verify that no unauthorized administrative accounts exist.
  • If upgrades are impossible, delete or revoke any existing shared-folder upload links to reduce the attack surface.

Generated by OpenCVE AI on August 10, 2026 at 23:12 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 10 Aug 2026 12:00:00 +0000

Type Values Removed Values Added
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 %). The raw filename is then passed to UploadModel::handleUpload, where it is reconstructed as trim(urldecode(basename($fileName))), re-introducing path separators after validation (e.g. ..%2fusers%2fusers.txt becomes ../users/users.txt). UploadNamePolicy::isAllowedForWrite() applies basename() internally and therefore only evaluates the final component (users.txt), allowing the traversal sequence to pass the extension policy. The destination path is then used directly in move_uploaded_file() with no realpath containment check, allowing a write outside the intended upload directory. An attacker who possesses a valid, non-expired, upload-enabled shared-folder link/token (which are designed to be shared publicly) can overwrite users/users.txt to create an administrator account, resulting in unauthenticated admin takeover and, depending on configuration, remote code execution. Exploitation requires possession of a valid, non-expired, upload-enabled shared-folder link/token. This issue is fixed in 3.16.0, which URL-decodes before validation and rejects any path separators in the upload filename. 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 %).
Title FileRise - Shared-Folder Upload Path Traversal Allows Arbitrary File Write and Admin Takeover FileRise shared-folder upload path traversal allows arbitrary file write and admin takeover

Mon, 10 Aug 2026 11:45:00 +0000

Type Values Removed Values Added
Title FileRise shared-folder upload path traversal allows arbitrary file write and admin takeover FileRise - Shared-Folder Upload Path Traversal Allows Arbitrary File Write and Admin Takeover

Mon, 22 Jun 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Fri, 19 Jun 2026 08:15:00 +0000

Type Values Removed Values Added
First Time appeared Error311
Error311 filerise
Vendors & Products Error311
Error311 filerise

Fri, 19 Jun 2026 06:15:00 +0000

Type Values Removed Values Added
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 %). The raw filename is then passed to UploadModel::handleUpload, where it is reconstructed as trim(urldecode(basename($fileName))), re-introducing path separators after validation (e.g. ..%2fusers%2fusers.txt becomes ../users/users.txt). UploadNamePolicy::isAllowedForWrite() applies basename() internally and therefore only evaluates the final component (users.txt), allowing the traversal sequence to pass the extension policy. The destination path is then used directly in move_uploaded_file() with no realpath containment check, allowing a write outside the intended upload directory. An attacker who possesses a valid, non-expired, upload-enabled shared-folder link/token (which are designed to be shared publicly) can overwrite users/users.txt to create an administrator account, resulting in unauthenticated admin takeover and, depending on configuration, remote code execution. Exploitation requires possession of a valid, non-expired, upload-enabled shared-folder link/token. This issue is fixed in 3.16.0, which URL-decodes before validation and rejects any path separators in the upload filename.
Title FileRise shared-folder upload path traversal allows arbitrary file write and admin takeover
Weaknesses CWE-22
CWE-434
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 9.3, 'vector': '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'}


Subscriptions

Error311 Filerise
cve-icon MITRE

Status: PUBLISHED

Assigner: TuranSec

Published:

Updated: 2026-08-10T11:44:02.512Z

Reserved: 2026-06-13T16:39:46.122Z

Link: CVE-2026-54414

cve-icon Vulnrichment

Updated: 2026-06-22T15:05:03.542Z

cve-icon NVD

Status : Deferred

Published: 2026-06-19T06:17:09.830

Modified: 2026-08-10T12:17:17.563

Link: CVE-2026-54414

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-10T23:15:05Z

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

  • CWE-434

    Unrestricted Upload of File with Dangerous Type