# CVE-2025-62509: FileRise improper ownership/permission validation allowed cross-tenant file operations

> Low-privilege users can view, delete, or modify other users' files due to missing server-side ownership checks in FileRise.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 Oct 2025
- **Updated:** 20 Oct 2025
- **Also known as:** GHSA-6p87-q9rh-95wh

## What is CVE-2025-62509?

CVE-2025-62509 is a high-severity missing authorization vulnerability in error311 FileRise, published on 20 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to version 1.4.0, a business logic flaw in FileRise’s file/folder handling allows low-privilege users to perform unauthorized operations (view/delete/modify) on files created by other users. The root cause was inferring ownership/visibility from folder names (e.g., a folder named after a username) and missing server-side authorization/ownership checks across file operation endpoints. This amounted to an IDOR pattern: an attacker could operate on resources identified only by predictable names. This issue has been patched in version 1.4.0 and further hardened in version 1.5.0. A workaround for this issue involves restricting non-admin users to read-only or disable delete/rename APIs server-side, avoid creating top-level folders named after other usernames, and adding server-side checks that verify ownership before delete/rename/move.

Weakness: CWE-284 (Improper Access Control), CWE-280 (Improper Handling of Insufficient Permissions or Privileges)

## Which versions are affected by CVE-2025-62509?

It affects 1 product.


Products: Filerise Filerise.

## How do I fix CVE-2025-62509?

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

## Is CVE-2025-62509 being exploited?

There is no known exploitation of CVE-2025-62509 in the wild and no public exploit code.

## 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-62510](https://insights.sbomify.com/CVE-2025-62510/): FileRise insecure folder visibility via name-based mapping and incomplete ACL checks (high 8.1)
- [CVE-2026-25231](https://insights.sbomify.com/CVE-2026-25231/): FileRise affected by an Unauthenticated File Read Due to Insufficient Access Control (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-62509 and fix it if it is affected.

What it is: CVE-2025-62509 is a high-severity missing authorization vulnerability in error311 FileRise, published on 20 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-62509 in the wild and no public exploit code.

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-2025-62509/ (Markdown: https://insights.sbomify.com/CVE-2025-62509/index.md)
```

## Sources

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

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