/

CVE-2026-33329

Severity:

HIGH RISK

(8.1)

Path Traversal in FileRise Resumable Upload Handler

CVE-2026-33329

Analyzed

Vulnerability type

Category:

Path Traversal

CWE:

CWE-22, CWE-73

Impact:

Arbitrary File Write and Directory Deletion by Authenticated Users

Severity:

HIGH RISK

(8.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

FileRise's resumable upload handler concatenates the resumableIdentifier parameter directly into filesystem paths without sanitization.

An authenticated user with upload permissions can abuse this to write files to arbitrary directories, delete arbitrary directories during cleanup, and probe for file and directory existence on the server.

Affected context

This vulnerability appears in FileRise deployments that expose the Resumable.js chunked upload feature and grant users upload permissions.

The issue resides in UploadModel::handleUpload(), where the resumableIdentifier parameter is incorporated into server-side filesystem paths without being normalized or checked for traversal sequences.

Any environment where authenticated users can control this parameter and the server has access to sensitive directories is potentially affected.

Exploit preconditions

  • Attack surface: HTTP interface to the FileRise resumable upload endpoint.
  • Required access: Valid authenticated account with permission to perform uploads.
  • Trigger point: Submission of crafted upload requests where resumableIdentifier contains path traversal patterns or manipulated path components.
  • Why exploitation is possible: The server constructs filesystem paths by concatenating the untrusted resumableIdentifier directly, without canonicalization, validation, or restriction to a dedicated upload root, enabling traversal outside the intended directory.

Why this happens

The core issue is improper neutralization of user-controlled path elements when constructing filesystem locations, aligning with CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').

By embedding the resumableIdentifier directly into on-disk paths, the upload handler allows user input to influence where files and directories are created, accessed, or deleted.

This behavior also overlaps with CWE-73: External Control of File Name or Path, because the application lets external input determine the effective file paths used by file system operations during upload assembly and post-upload cleanup.

Potential impact

  • Authenticated users may write arbitrary files into directories accessible by the FileRise process.
  • Attackers could delete arbitrary directories reachable by the cleanup routine, causing data loss or denial of service.
  • File and directory existence probing can be used to map the server filesystem and discover sensitive structure.
  • In some environments, arbitrary file writes could enable further compromise (for example, writing executable or interpretable files into web-served directories).

General mitigation guidance

Effective mitigation focuses on confining and validating all filesystem interactions influenced by user-controlled parameters:

  • Restrict uploads to a dedicated, application-controlled directory and never allow client input to alter the base path.
  • Normalize and canonicalize any path components and reject values that resolve outside the intended upload root or contain traversal elements such as ../.
  • Map user-supplied identifiers (like resumableIdentifier) to internal, server-generated filenames or directory names instead of using them directly.
  • Enforce strict allowlists for characters and patterns in identifiers and filenames, rejecting unexpected or complex path constructions.
  • Run the application under a least-privileged account with minimal filesystem permissions to limit the impact of any remaining path misuses.

How teams detect issues like this

Organizations can look for this class of issue through a combination of code and behavior analysis:

  • Static analysis rules that flag direct concatenation of request parameters into filesystem paths, especially where no canonicalization or root enforcement is present.
  • Code review checklists that require reviewers to verify that all file operations use fixed base directories and validate user-controlled path segments.
  • Runtime logging and monitoring for unusual upload paths, failed file operations in unexpected directories, or repeated cleanup failures.
  • Security testing that includes targeted path traversal tests against upload endpoints, using automated scanners or custom scripts to attempt directory escapes.

Sources

SourceLink
github.comgithub.com/error311/FileRise/commit/3871f9fd1661688bed4f7dd23912be0ebf50973c
github.comgithub.com/error311/FileRise/releases/tag/v3.10.0
github.comgithub.com/error311/FileRise/security/advisories/GHSA-c2jm-4wp9-5vrh

Frequently asked

questions

Yes. Any user who can reach the FileRise web interface and authenticate with upload permissions can send crafted upload requests to exploit the path traversal behavior.

No administrative privileges are required, but the attacker must have a valid account with upload rights. The impact is then limited by the filesystem permissions of the FileRise process and where it is allowed to read and write.

The most robust fix is to decouple user input from filesystem paths: enforce a fixed upload root, map client-provided identifiers to internal names, and reject any path that would resolve outside the allowed directory after canonicalization.

Adopt secure file handling patterns as a standard: perform strict input validation on all path components, use path-joining helpers that enforce root confinement, include path traversal checks in code review and CI pipelines, and apply least-privilege filesystem permissions to reduce the blast radius of any mistakes.

Find out what's already
exploitable in your codebase.