Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:HSummary
CVE-2026-33329 is a high-severity Path Traversal (CWE-22) vulnerability in Filerise Filerise. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-33329 is a path traversal vulnerability (CWE-22, CWE-73) affecting FileRise, a self-hosted web file manager and WebDAV server. In versions 1.0.1 through 3.9.x, the resumableIdentifier parameter in the Resumable.js chunked upload handler (UploadModel::handleUpload()) is directly concatenated into filesystem paths without sanitization, enabling directory traversal attacks. The vulnerability carries a CVSS v3.1 base score of 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H) and was published on 2026-03-24.
An authenticated user with upload permissions can exploit this flaw remotely over the network with low complexity. By crafting the resumableIdentifier parameter with traversal sequences (e.g., ../), attackers can write uploaded file chunks to arbitrary server directories, assemble them into malicious files, delete arbitrary directories during post-assembly cleanup, and probe for the existence of files or directories.
The issue is addressed in FileRise version 3.10.0, where sanitization was added to the resumableIdentifier handling. Security practitioners should upgrade to this version immediately. Relevant resources include the patching commit at https://github.com/error311/FileRise/commit/3871f9fd1661688bed4f7dd23912be0ebf50973c, the release notes at https://github.com/error311/FileRise/releases/tag/v3.10.0, and the GitHub security advisory at https://github.com/error311/FileRise/security/advisories/GHSA-c2jm-4wp9-5vrh.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-14992
Vulnerability Data
FileRise is a self-hosted web file manager / WebDAV server. From version 1.0.1 to before version 3.10.0, the resumableIdentifier parameter in the Resumable.js chunked upload handler (UploadModel::handleUpload()) is concatenated directly into filesystem paths without any sanitization. An authenticated user with…
more
upload permission can exploit this to write files to arbitrary directories on the server, delete arbitrary directories via the post-assembly cleanup, and probe file/directory existence. This issue has been patched in version 3.10.0.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Input validation directly neutralizes special path elements before pathname construction occurs.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices include input validation and path sanitization that eliminate this weakness.
Least-privilege file authorization directly limits damage from externally controlled paths.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches path traversal via static/dynamic analysis.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Information access restriction limits which files an application may read or write.