CVE-2026-54414: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in error311 FileRise
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.
AI Analysis
Technical Summary
CVE-2026-54414 is a critical path traversal vulnerability in FileRise before version 3.16.0. The shared-folder upload endpoint (/api/folder/uploadToSharedFolder.php) improperly validates upload filenames by applying basename() and a regex that blocks '/' and '\' but not URL-encoded equivalents like '%2f'. The raw filename is then urldecoded and reconstructed, reintroducing path separators that bypass validation. The UploadNamePolicy only checks the final filename component, allowing traversal sequences to pass extension policies. The vulnerable code uses move_uploaded_file() without realpath containment checks, enabling arbitrary file writes outside the intended directory. An attacker with a valid, non-expired, upload-enabled shared-folder link/token can overwrite files such as users/users.txt to create an administrator account, leading to unauthenticated admin takeover and possible remote code execution depending on configuration. The vulnerability is fixed in version 3.16.0 by decoding the filename before validation and rejecting any path separators.
Potential Impact
An attacker who obtains a valid, non-expired, upload-enabled shared-folder link/token can exploit this vulnerability to write arbitrary files outside the designated upload directory. This can result in unauthorized administrator account creation, leading to full administrative control of the FileRise instance without authentication. Depending on the system configuration, this may also enable remote code execution. The vulnerability thus compromises confidentiality, integrity, and availability of the affected system.
Mitigation Recommendations
A fix is available in FileRise version 3.16.0, which properly URL-decodes filenames before validation and rejects any path separators in upload filenames. Users should upgrade to version 3.16.0 or later to remediate this vulnerability. Until upgraded, restrict access to valid, non-expired, upload-enabled shared-folder links/tokens to trusted users only. Patch status is confirmed fixed in 3.16.0.
CVE-2026-54414: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in error311 FileRise
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.
CVSS v3.1
Score 9.8critical
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-54414 is a critical path traversal vulnerability in FileRise before version 3.16.0. The shared-folder upload endpoint (/api/folder/uploadToSharedFolder.php) improperly validates upload filenames by applying basename() and a regex that blocks '/' and '\' but not URL-encoded equivalents like '%2f'. The raw filename is then urldecoded and reconstructed, reintroducing path separators that bypass validation. The UploadNamePolicy only checks the final filename component, allowing traversal sequences to pass extension policies. The vulnerable code uses move_uploaded_file() without realpath containment checks, enabling arbitrary file writes outside the intended directory. An attacker with a valid, non-expired, upload-enabled shared-folder link/token can overwrite files such as users/users.txt to create an administrator account, leading to unauthenticated admin takeover and possible remote code execution depending on configuration. The vulnerability is fixed in version 3.16.0 by decoding the filename before validation and rejecting any path separators.
Potential Impact
An attacker who obtains a valid, non-expired, upload-enabled shared-folder link/token can exploit this vulnerability to write arbitrary files outside the designated upload directory. This can result in unauthorized administrator account creation, leading to full administrative control of the FileRise instance without authentication. Depending on the system configuration, this may also enable remote code execution. The vulnerability thus compromises confidentiality, integrity, and availability of the affected system.
Mitigation Recommendations
A fix is available in FileRise version 3.16.0, which properly URL-decodes filenames before validation and rejects any path separators in upload filenames. Users should upgrade to version 3.16.0 or later to remediate this vulnerability. Until upgraded, restrict access to valid, non-expired, upload-enabled shared-folder links/tokens to trusted users only. Patch status is confirmed fixed in 3.16.0.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- TuranSec
- Date Reserved
- 2026-06-13T16:39:46.122Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a34df99f198dc38c19de735
Added to database: 6/19/2026, 6:20:09 AM
Last enriched: 6/19/2026, 6:35:13 AM
Last updated: 6/19/2026, 9:58:10 PM
Views: 29
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.