# CVE-2026-25231: FileRise affected by an Unauthenticated File Read Due to Insufficient Access Control

> Unauthenticated attackers can read files from the uploads directory in FileRise due to missing access controls, exposing sensitive data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Feb 2026
- **Updated:** 10 Feb 2026
- **Also known as:** GHSA-hv99-77cw-hvpr

## What is CVE-2026-25231?

CVE-2026-25231 is a high-severity missing authorization vulnerability in error311 FileRise, published on 9 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FileRise is a self-hosted web file manager / WebDAV server. Versions prior to 3.3.0, the application contains an unauthenticated file read vulnerability due to the lack of access control on the /uploads directory. Files uploaded to this directory can be accessed directly by any user who knows or can guess the file path, without requiring authentication. As a result, sensitive data could be exposed, and privacy may be breached. This vulnerability is fixed in 3.3.0.

Weakness: CWE-552 (Files or Directories Accessible to External Parties), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Filerise Filerise.

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

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

## Is CVE-2026-25231 being exploited?

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

Public exploit code:

- FileRise <= 3.3.0 - Unauthenticated File Read (nuclei): http/cves/2026/CVE-2026-25231.yaml

## 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-25231 and fix it if it is affected.

What it is: CVE-2026-25231 is a high-severity missing authorization vulnerability in error311 FileRise, published on 9 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25231 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-25231/ (Markdown: https://insights.sbomify.com/CVE-2026-25231/index.md)
```

## Sources

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

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