CVE-2026-33329

8.1

error311 · FileRise

A path traversal vulnerability in FileRise allows authenticated users to achieve arbitrary file writes and directory deletion via the resumableIdentifier parameter in the chunked upload handler.

Executive summary

FileRise versions 1.0.1 through 3.10.0 are vulnerable to a path traversal attack that allows authenticated users to perform unauthorized file system operations, posing a high risk to data integrity and availability.

Vulnerability

The vulnerability exists in the UploadModel::handleUpload function, where the resumableIdentifier parameter is improperly sanitized before being used in file system operations. An authenticated user with upload privileges can exploit this to write files to arbitrary locations or delete directories on the host server.

Business impact

The ability for an authenticated user to write or delete files arbitrarily can lead to complete system compromise, including the injection of malicious scripts or the destruction of critical application data. Given the CVSS score of 8.1, this flaw presents a high risk to business operations, potentially resulting in significant downtime or unauthorized data manipulation.

Remediation

Immediate Action: Update FileRise to version 3.10.0 or later immediately to resolve the path sanitization flaw.

Proactive Monitoring: Review web access logs for unusual POST requests targeting the chunked upload endpoint, particularly those containing path traversal sequences like double dots and slashes.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block path traversal attempts and suspicious file path characters in request parameters.

Exploitation status

Public Exploit Available: No (exploit_available: unknown).

Analyst recommendation

The severity of this vulnerability, combined with the availability of proof-of-concept information, necessitates immediate action. Administrators must prioritize updating to version 3.10.0 to eliminate the underlying flaw. If an immediate update is not feasible, restrict upload permissions and implement robust WAF filtering to prevent exploitation until the patch can be deployed.

Sources