CVE-2026-33071 | error311 FileRise up to 3.7.x WebDAV Upload Endpoint createFile unrestricted upload

VDB-352035 · CVE-2026-33071 · GCVE-0-2026-33071 ERROR311 FILERISE UP TO 3.7.X WEBDAV UPLOAD ENDPOINT CREATEFILE UNRESTRICTED UPLOAD HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.2 $0-$5k 2.02+ Summaryinfo A vulnerability was found in error311 FileRise up to 3.7.x. It has been classified as critical. This affects the function createFile of the component WebDAV Upload Endpoint. Performing a manipulation results in unrestricted upload. This vulnerability is known as CVE-2026-33071. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended. Detailsinfo A vulnerability classified as critical has been found in error311 FileRise up to 3.7.x. This affects the function createFile of the component WebDAV Upload Endpoint. The manipulation with an unknown input leads to a unrestricted upload vulnerability. CWE is classifying the issue as CWE-434. The product allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is: FileRise is a self-hosted web file manager / WebDAV server. In versions prior to 3.8.0, the WebDAV upload endpoint accepts any file extension including .phtml, .php5, .htaccess, and other server-side executable types, bypassing the filename validation enforced by the regular upload path. In non-default deployments lacking Apache's LocationMatch protection, this leads to remote code execution. When files are uploaded via WebDAV, the createFile() method in FileRiseDirectory.php and the put() method in FileRiseFile.php accept the filename directly from the WebDAV client without any validation. In contrast, the regular upload endpoint in UploadModel::upload() validates filenames against REGEX_FILE_NAME. This issue is fixed in version 3.8.0. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-33071 since 03/17/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1608.002 according to MITRE ATT&CK. Upgrading to version 3.8.0 eliminates this vulnerability. Productinfo Vendor error311 Name FileRise Version 3.0 3.1 3.2 3.3 3.4 3.5 3.6 3.7 Website Product: https://github.com/error311/FileRise/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 5.3 VulDB Meta Temp Score: 5.2 VulDB Base Score: 6.3 VulDB Temp Score: 6.0 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 4.3 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Unrestricted upload CWE: CWE-434 / CWE-284 / CWE-266 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: FileRise 3.8.0 Timelineinfo 03/17/2026 CVE reserved 03/20/2026 +3 days Advisory disclosed 03/20/2026 +0 days VulDB entry created 03/20/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: github.com Status: Confirmed CVE: CVE-2026-33071 (🔒) GCVE (CVE): GCVE-0-2026-33071 GCVE (VulDB): GCVE-100-352035 Entryinfo Created: 03/20/2026 10:11 Changes: 03/20/2026 10:11 (65) Complete: 🔍 Cache ID: 99:F43:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸