CVE-2026-33071: CWE-434: Unrestricted Upload of File with Dangerous Type in error311 FileRise
CVE-2026-33071 is a medium severity vulnerability in FileRise versions prior to 3. 8. 0, a self-hosted web file manager and WebDAV server. The vulnerability arises because the WebDAV upload endpoint does not validate file extensions, allowing attackers to upload files with dangerous server-side executable extensions such as . php, . phtml, and . htaccess. This bypasses the filename validation enforced on the regular upload path. In deployments without Apache's LocationMatch protection, this can lead to remote code execution. The flaw is due to the createFile() and put() methods accepting filenames directly from WebDAV clients without validation.
AI Analysis
Technical Summary
FileRise is a self-hosted web file manager and WebDAV server that prior to version 3.8.0 contained a vulnerability (CVE-2026-33071) related to unrestricted file uploads via its WebDAV interface. Specifically, the WebDAV upload endpoint accepts any file extension, including potentially dangerous server-side executable types such as .phtml, .php5, and .htaccess. This occurs because the createFile() method in FileRiseDirectory.php and the put() method in FileRiseFile.php accept filenames directly from the WebDAV client without performing validation. In contrast, the regular upload endpoint uses a regex-based filename validation (REGEX_FILE_NAME) to restrict uploads to safe file types. The lack of validation on the WebDAV path allows attackers to upload malicious scripts that can be executed by the server if the deployment does not have Apache's LocationMatch directive configured to block execution in the upload directory. This can lead to remote code execution (RCE), allowing attackers to execute arbitrary code on the server. The vulnerability is classified under CWE-434 (Unrestricted Upload of File with Dangerous Type) and CWE-552 (Files or Directories Accessible to External Parties). The CVSS 3.1 base score is 4.3 (medium), reflecting that the attack vector is network-based, requires low attack complexity, and requires privileges (PR:L) but no user interaction. The vulnerability affects all FileRise versions prior to 3.8.0 and was publicly disclosed on March 20, 2026. No known exploits have been reported in the wild to date. The issue is resolved in version 3.8.0 by implementing proper filename validation on the WebDAV upload endpoint.
Potential Impact
The primary impact of this vulnerability is the potential for remote code execution on servers running vulnerable versions of FileRise without proper Apache LocationMatch protections. Successful exploitation would allow attackers to upload malicious server-side scripts that can be executed, compromising the confidentiality, integrity, and availability of the affected system. This could lead to unauthorized access, data theft, defacement, or further network pivoting. Organizations using FileRise as a web file manager or WebDAV server, especially those exposing it to the internet, face increased risk of compromise. Since the vulnerability requires low attack complexity and network access with some privileges, insider threats or attackers who have gained limited access could escalate their control. The lack of user interaction needed increases the risk of automated exploitation once an attacker gains access. However, the medium CVSS score reflects that exploitation requires some privileges and specific server configurations lacking Apache protections. The vulnerability could disrupt business operations, lead to data breaches, and damage organizational reputation if exploited.
Mitigation Recommendations
Organizations should immediately upgrade FileRise to version 3.8.0 or later, where the vulnerability is fixed by enforcing filename validation on the WebDAV upload endpoint. Until upgrading, administrators should implement strict Apache LocationMatch directives or equivalent web server configurations to prevent execution of uploaded files in the WebDAV directories. Restrict WebDAV access to trusted users and networks only, employing strong authentication and network segmentation. Monitor WebDAV upload directories for suspicious files, especially those with executable extensions like .php, .phtml, or .htaccess. Employ file integrity monitoring and intrusion detection systems to detect unauthorized uploads or execution attempts. Regularly audit server configurations to ensure that upload directories are not executable. Consider disabling WebDAV if not required or replacing it with more secure file transfer mechanisms. Finally, maintain up-to-date backups and incident response plans to recover quickly if exploitation occurs.
Affected Countries
United States, Germany, United Kingdom, France, Japan, Australia, Canada, Netherlands, South Korea, India
CVE-2026-33071: CWE-434: Unrestricted Upload of File with Dangerous Type in error311 FileRise
Description
CVE-2026-33071 is a medium severity vulnerability in FileRise versions prior to 3. 8. 0, a self-hosted web file manager and WebDAV server. The vulnerability arises because the WebDAV upload endpoint does not validate file extensions, allowing attackers to upload files with dangerous server-side executable extensions such as . php, . phtml, and . htaccess. This bypasses the filename validation enforced on the regular upload path. In deployments without Apache's LocationMatch protection, this can lead to remote code execution. The flaw is due to the createFile() and put() methods accepting filenames directly from WebDAV clients without validation.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
FileRise is a self-hosted web file manager and WebDAV server that prior to version 3.8.0 contained a vulnerability (CVE-2026-33071) related to unrestricted file uploads via its WebDAV interface. Specifically, the WebDAV upload endpoint accepts any file extension, including potentially dangerous server-side executable types such as .phtml, .php5, and .htaccess. This occurs because the createFile() method in FileRiseDirectory.php and the put() method in FileRiseFile.php accept filenames directly from the WebDAV client without performing validation. In contrast, the regular upload endpoint uses a regex-based filename validation (REGEX_FILE_NAME) to restrict uploads to safe file types. The lack of validation on the WebDAV path allows attackers to upload malicious scripts that can be executed by the server if the deployment does not have Apache's LocationMatch directive configured to block execution in the upload directory. This can lead to remote code execution (RCE), allowing attackers to execute arbitrary code on the server. The vulnerability is classified under CWE-434 (Unrestricted Upload of File with Dangerous Type) and CWE-552 (Files or Directories Accessible to External Parties). The CVSS 3.1 base score is 4.3 (medium), reflecting that the attack vector is network-based, requires low attack complexity, and requires privileges (PR:L) but no user interaction. The vulnerability affects all FileRise versions prior to 3.8.0 and was publicly disclosed on March 20, 2026. No known exploits have been reported in the wild to date. The issue is resolved in version 3.8.0 by implementing proper filename validation on the WebDAV upload endpoint.
Potential Impact
The primary impact of this vulnerability is the potential for remote code execution on servers running vulnerable versions of FileRise without proper Apache LocationMatch protections. Successful exploitation would allow attackers to upload malicious server-side scripts that can be executed, compromising the confidentiality, integrity, and availability of the affected system. This could lead to unauthorized access, data theft, defacement, or further network pivoting. Organizations using FileRise as a web file manager or WebDAV server, especially those exposing it to the internet, face increased risk of compromise. Since the vulnerability requires low attack complexity and network access with some privileges, insider threats or attackers who have gained limited access could escalate their control. The lack of user interaction needed increases the risk of automated exploitation once an attacker gains access. However, the medium CVSS score reflects that exploitation requires some privileges and specific server configurations lacking Apache protections. The vulnerability could disrupt business operations, lead to data breaches, and damage organizational reputation if exploited.
Mitigation Recommendations
Organizations should immediately upgrade FileRise to version 3.8.0 or later, where the vulnerability is fixed by enforcing filename validation on the WebDAV upload endpoint. Until upgrading, administrators should implement strict Apache LocationMatch directives or equivalent web server configurations to prevent execution of uploaded files in the WebDAV directories. Restrict WebDAV access to trusted users and networks only, employing strong authentication and network segmentation. Monitor WebDAV upload directories for suspicious files, especially those with executable extensions like .php, .phtml, or .htaccess. Employ file integrity monitoring and intrusion detection systems to detect unauthorized uploads or execution attempts. Regularly audit server configurations to ensure that upload directories are not executable. Consider disabling WebDAV if not required or replacing it with more secure file transfer mechanisms. Finally, maintain up-to-date backups and incident response plans to recover quickly if exploitation occurs.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-17T19:27:06.344Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69bd0b4ce32a4fbe5f4933b4
Added to database: 3/20/2026, 8:54:36 AM
Last enriched: 3/27/2026, 7:32:17 PM
Last updated: 4/30/2026, 4:52:46 PM
Views: 69
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.