---
id: CVE-2025-62509
title: >-
  FileRise is a self-hosted web-based file manager with multi-file upload,
  editing, and batch operations
summary: >-
  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 o…
severity: high
cvss: 8.1
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'
cwe:
  - CWE-280
  - CWE-284
vendor: filerise
product: filerise
affected:
  - filerise < 1.4.0
patched:
  - filerise 1.4.0
published: '2025-10-20'
updated: '2026-10-08'
sourceUpdated: '2026-10-08T22:10:00.563'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2025-62509'
references:
  - url: >-
      https://github.com/error311/FileRise/commit/25ce6a76beb60950359c0304765ad91a8aff8ad8
    label: security-advisories@github.com
  - url: 'https://github.com/error311/FileRise/issues/53'
    label: security-advisories@github.com
  - url: >-
      https://github.com/error311/FileRise/security/advisories/GHSA-6p87-q9rh-95wh
    label: security-advisories@github.com
tags:
  - nvd
epss: 0.00306
epssPercentile: 0.21404
ingestedAt: '2026-10-08T22:11:53.820Z'
---

## Overview

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.

## Affected

- `filerise < 1.4.0`

## Remediation

Upgrade past the affected range:

- `filerise 1.4.0`