# CVE-2026-33071: FileRise: WebDAV upload path bypasses filename validation enforced by regular uploads

> Attackers can upload executable files via WebDAV to achieve remote code execution in FileRise deployments lacking specific Apache protections.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** GHSA-46gv-gf5f-wvr2

## What is CVE-2026-33071?

CVE-2026-33071 is a medium-severity vulnerability in error311 FileRise, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-552 (Files or Directories Accessible to External Parties), CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2026-33071?

It affects 1 product.


Products: Filerise Filerise.

## How do I fix CVE-2026-33071?

No fix has been published for CVE-2026-33071 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33071 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33071 exists.

## Other vulnerabilities in error311 FileRise

- [CVE-2025-68116](https://insights.sbomify.com/CVE-2025-68116/): FileRise vulnerable to Cross-Site Scripting (XSS) in SVG File Handling (high 8.9)
- [CVE-2026-33072](https://insights.sbomify.com/CVE-2026-33072/): FileRise: Default Encryption Key Enables Token Forgery and Config Decryption (high 8.2)
- [CVE-2026-33329](https://insights.sbomify.com/CVE-2026-33329/): Path traversal in FileRise (high 8.1)
- [CVE-2025-62509](https://insights.sbomify.com/CVE-2025-62509/): FileRise improper ownership/permission validation allowed cross-tenant file operations (high 8.1)
- [CVE-2025-62510](https://insights.sbomify.com/CVE-2025-62510/): FileRise insecure folder visibility via name-based mapping and incomplete ACL checks (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33071 and fix it if it is affected.

What it is: CVE-2026-33071 is a medium-severity vulnerability in error311 FileRise, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33071 exists.

Affected product: error311 FileRise. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33071/ (Markdown: https://insights.sbomify.com/CVE-2026-33071/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33071
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33071
- OSV: https://osv.dev/vulnerability/CVE-2026-33071

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33071/
Summaries are generated and may contain mistakes; the official description above is the record.