Skip to main content

FileRise CVE-2026-54414

| EUVDEUVD-2026-37993 CRITICAL
Path Traversal (CWE-22)
2026-06-19 TuranSec GHSA-jg2q-3m38-6xc2
9.3
CVSS 4.0 · Vendor: TuranSec
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Obtain public shared-folder upload link
  2. Delivery
    Craft multipart upload with URL-encoded traversal filename
  3. Exploit
    Bypass FolderController regex validation
  4. Install
    urldecode in UploadModel reintroduces separators
  5. C2
    move_uploaded_file writes users/users.txt outside upload dir
  6. Execute
    Authenticate as planted administrator
  7. Impact
    Pivot to RCE via admin functionality

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK

2 techniques across 2 tactics: Discovery, Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Attacker must possess a valid, non-expired, upload-enabled shared-folder link/token for the target FileRise instance - these tokens are by design intended to be shared publicly, so possession does not equate to authentication, but the endpoint /api/folder/uploadToSharedFolder.php is not reachable without one. The target must be running FileRise prior to 3.16.0 with the shared-folder upload feature in use, and must be network-reachable to the attacker. No user interaction, no admin credentials, no second-factor, and no specific platform constraint are required beyond a standard PHP deployment of FileRise.

Impact

Risk is high and concrete. The CVSS 4.0 vector AV:N/AC:L/AT:N/PR:N/UI:N with VC:H/VI:H/VA:H accurately reflects a network-reachable, unauthenticated, no-interaction primitive that yields full compromise via users.txt overwrite. The 'PR:N' rating is defensible because the required token is, by design, a publicly shareable link rather than an authentication credential - this is the kind of nuance that distinguishes a real priority from a paper tiger. No KEV listing and no public exploit identified at time of analysis temper urgency slightly, but the v3.16.0 release notes publicly describe the bypass ('reject encoded path separators before upload writes'), which makes patch-diffing trivial and shortens the time-to-exploit window. EPSS data was not provided in the input, so probabilistic exploitation likelihood cannot be quoted; treat this as a near-term patching priority for any internet-exposed FileRise instance issuing shared-folder upload links.

Exploit ScenarioDerived

An attacker obtains a public upload-enabled shared-folder link (posted on a forum, leaked via search engines, or shared through social channels) and submits a multipart upload to /api/folder/uploadToSharedFolder.php with a filename like '..%2fusers%2fusers.txt' whose body contains a crafted users.txt entry granting the attacker administrator role. The server decodes the name after validation and writes the file outside the upload directory, replacing the user database; the attacker then logs in as administrator and, depending on configuration, leverages the admin UI to achieve remote code execution. No public PoC has been identified at time of analysis, but the patch notes disclose the bypass primitive.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.7% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 19, 2026

Unauthenticated administrator account takeover in FileRise before 3.16.0 is possible via a path traversal flaw in the shared-folder upload endpoint (/api/folder/uploadToSharedFolder.php), where URL-encoded path separators bypass filename validation and allow arbitrary file write outside the upload directory. Any actor holding a valid, non-expired, upload-enabled shared-folder token - tokens explicitly designed to be shared publicly - can overwrite users/users.txt to plant an admin account and, depending on configuration, achieve remote code execution. No public exploit identified at time of analysis, but the upstream fix in v3.16.0 documents the exact bypass, lowering the bar for weaponization.

RemediationAI

Vendor-released patch: upgrade to FileRise v3.16.0 or later (https://github.com/error311/FileRise/releases/tag/v3.16.0), which URL-decodes before validation and rejects any path separators in the upload filename. If immediate upgrade is not feasible, revoke or expire all existing upload-enabled shared-folder tokens and disable creation of new upload-enabled share links (read-only shares are unaffected by this specific endpoint flaw); this breaks the public-upload feature but removes the attack precondition. As an additional containment step, place /api/folder/uploadToSharedFolder.php behind an authenticating reverse proxy or block it at the web server, accepting that legitimate public uploads will stop working. After patching, audit users/users.txt and the upload directory tree for unexpected admin entries or files written outside the intended upload root, and rotate all admin credentials and remember-me tokens, since the v3.16.0 notes show other auth-related hardening was bundled in the same release.

Affected VersionsENISA

FileRise 0 <3.16.0

Affected Packages

euvd filerise fix: 3.16.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

FileRise is a PHP-based self-hosted web file manager (CPE cpe:2.3:a:error311:filerise). The flaw is a classic CWE-22 Path Traversal caused by an order-of-operations defect between validation and decoding: FolderController applies basename() and the REGEX_FILE_NAME allowlist (which rejects literal '/' and '\' but permits '%') against the raw filename, after which UploadModel::handleUpload reconstructs the name via trim(urldecode(basename($fileName))). Decoding after validation re-introduces separators (e.g. '..%2fusers%2fusers.txt' becomes '../users/users.txt'), and the secondary UploadNamePolicy::isAllowedForWrite() check itself calls basename() so the policy only inspects the final component. The destination is passed directly to move_uploaded_file() with no realpath() containment, so the writer escapes the upload directory entirely.

Know when Filerise gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (TuranSec) PRIMARY 9.3 CRITICAL
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
vuln.today AI 9.8 CRITICAL

Network-reachable upload endpoint, no auth (token is public by design = PR:N), no user interaction, low complexity, and users.txt overwrite yields full admin compromise across C/I/A.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (TuranSec).

CVSS VectorVendor: TuranSec

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

1
CVSS changed
Jun 19, 2026 - 06:22 NVD
9.8 (CRITICAL) 9.3 (CRITICAL)

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

FileRise versions before 3.16.0 contain a critical path traversal flaw in the shared-folder upload endpoint that allows any actor with a valid shared-folder token to create administrative accounts and potentially achieve remote code execution. No public exploit identified at time of analysis, but organizations using FileRise face immediate risk of account compromise and system takeover; the published fix documentation has lowered the barrier to exploitation.

Business Impact: Severe
Compensating Controls

Vendor-released patch: FileRise 3.16.0 or later.

Threat Intelligence Overview

EPSS Score
0.7%
Top 51% exploitable
Social Media
3
Sightings
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment CIRCL GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.7%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

47
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

CVE-2026-25231 HIGH POC
7.5 Feb 09

Unauthenticated directory traversal in FileRise prior to version 3.3.0 allows remote attackers to read arbitrary files f

CVE-2025-66403 MEDIUM POC
5.4 Dec 01

Stored cross-site scripting in FileRise versions before 2.2.3 allows an authenticated user with upload rights to embed J

CVE-2026-25230 MEDIUM POC
4.6 Feb 09

FileRise versions before 3.3.0 contain an HTML injection vulnerability that allows authenticated users to manipulate the

CVE-2026-61843 HIGH
8.2 Oct 14

File overwrite in FileRise prior to 3.18.0 allows an unauthenticated visitor who holds a valid upload-enabled shared-fol

CVE-2026-33072 HIGH
8.2 Mar 20

FileRise, a self-hosted web file manager and WebDAV server, contains a critical hardcoded encryption key vulnerability i

CVE-2026-57489 HIGH
8.1 Oct 14

Authentication bypass in FileRise (CWE-290) lets unauthenticated remote attackers impersonate any account - including an

CVE-2026-103977 HIGH
8.1 Oct 14

Online second-factor guessing against FileRise releases prior to 3.23.0 is permitted well beyond the intended limit beca

CVE-2026-57490 HIGH
8.1 Oct 14

Multi-factor authentication bypass in FileRise WebDAV prior to 3.16.0 allows an attacker who already holds a valid usern

CVE-2026-104108 HIGH
8.1 Oct 14

Authentication bypass in FileRise versions before 3.23.0 lets a remote attacker log in as an existing local account - in

CVE-2026-33329 HIGH
8.1 Mar 24

FileRise, a self-hosted web file manager and WebDAV server, contains a path traversal vulnerability in its Resumable.js

CVE-2025-62510 HIGH
8.1 Oct 20

FileRise 1.4.0 exposes folder visibility and ownership decisions to authenticated low-privilege users because a regressi

CVE-2025-62509 HIGH
8.1 Oct 20

Low-privilege users of FileRise versions prior to 1.4.0 can view, delete, or modify files owned by other users because t

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy