Skip to main content

FileRise CVE-2025-62510

HIGH
Improper Handling of Insufficient Permissions or Privileges (CWE-280)
2025-10-20 security-advisories@github.com
8.1
CVSS 3.1 · Vendor: github
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privilege FileRise user
  2. Exploit
    Enumerate folders by username/name inference
  3. Execution
    Access other users' folder contents
  4. Impact
    Read or rename/move/copy their files

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V8 - Authorization Insufficient permission handling
Exploitation Conditions

Exploitation requires an authenticated low-privilege FileRise account on a vulnerable v1.4.0 instance; the per-request condition is the v1.4.0 regression where folder visibility/ownership is derived from folder names, so folders whose names match the attacker's username (and, in some cases, other users' folders) become accessible across list, read, write, share, rename, copy/move, zip, and WebDAV code paths. Limiting factors: the attacker must already hold valid credentials (PR:L - not remote-unauthenticated), the instance must be the specific regressed version 1.4.0 (fixed in 1.5.0), and the flaw primarily benefits multi-user deployments - a single-user instance has no other users' content to expose.

Impact

This is a credible, upgrade-worthy access-control flaw but not a drop-everything emergency. The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N, base 8.1) indicates a network-reachable, low-complexity attack that requires an existing low-privilege authenticated account (PR:L) and no user interaction, yielding high confidentiality and integrity impact - consistent with the CWE-280 broken-access-control description. No EPSS score, KEV listing, POC, or SSVC decision data was supplied, so there is no evidence of active or automated exploitation; exploitation status is best characterized as no public exploit identified at time of analysis. The main signal tension is between the high CVSS (8.1) and the real-world picture: the PR:L requirement means an attacker must already hold a FileRise account, and FileRise is a niche self-hosted product, which constrains mass exploitation despite the network vector. Treat this as a genuine confidentiality/integrity risk on any multi-user FileRise 1.4.0 instance, prioritized by how sensitive the hosted files are and how many low-trust users have accounts, rather than as a wormable internet-wide threat.

Exploit ScenarioDerived

A legitimate low-privilege user of a shared FileRise 1.4.0 instance notices that folders whose names match their username are exposed to them, and leverages the name-based ownership inference regression to list, read, and in some cases rename, move, copy, or download folders and files belonging to other users. No public proof-of-concept is known, and no special tooling is required - the attacker simply operates through the normal web/WebDAV interface using their authenticated session, exploiting the low attack complexity (AC:L).

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 08, 2026

FileRise 1.4.0 exposes folder visibility and ownership decisions to authenticated low-privilege users because a regression derives access from folder names instead of an explicit access-control list, letting an attacker list, read, write, share, rename, copy/move, zip, and even reach over WebDAV folders they should not own - including folders named after their own username and, in some cases, other users' content. The flaw requires a valid low-privilege account (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N, score 8.1), so it is an authenticated privilege-boundary failure rather than a pre-auth remote compromise, and it primarily matters in multi-user deployments where other users' files actually exist. No public exploit code has been identified at time of analysis and CISA KEV does not list this CVE; the vendor patched the issue in FileRise 1.5.0, which introduces explicit per-folder ACLs and removes name-based ownership assumptions.

RemediationAI

Upgrade to FileRise 1.5.0, the exact vendor-released fix version, which introduces the per-folder ACL model (owners/read/write/share/read_own) and strict server-side checks; the change is published in commit b6d86b78967baa2f5a1e191903fc4df13998d87f and documented through the GitHub advisory GHSA-jm96-2w52-5qjj and issue 55, and the vendor's SECURITY.md now declares only v1.5.x supported. Because the upgrade is behavior-changing, plan a post-upgrade configuration pass rather than a blind drop-in: review the admin Folder Access grid and explicitly grant View (all) to users who need cross-folder visibility and View (own) to uploaders who should see only their own files, verifying that users previously configured as 'upload but not view' now hold Upload plus View (own) - otherwise legitimate workflows break because write no longer implies read. Then validate representative accounts against WebDAV to confirm read shows full listings, read_own shows only the caller's files, and writes succeed only where explicitly granted. If upgrading is not immediately possible, temporary compensating controls are limited and carry real trade-offs: constrain the instance to a single-user deployment or disable the WebDAV endpoint, since a single-user instance has no other users' content to expose, or rename any folder that matches a username so it no longer triggers name-based inference - though this last measure is fragile, does not address all code paths (share, zip, copy/move), and may break existing share links or bookmarks. Restricting network access to the FileRise listener only reduces the pool of already-authenticated callers and does not remediate the authorization flaw itself.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause class is CWE-280 (Improper Handling of Insufficient Privileges): FileRise's pre-1.5.0 permission model inferred folder visibility and ownership from folder names rather than from a stored, per-folder authorization record, so a folder whose name matched a caller's username (and in some paths other users' folders) was treated as theirs. The 1.5.0 fix, visible in commit b6d86b78967baa2f5a1e191903fc4df13998d87f, replaces this with explicit ACL buckets - owners, read, write, share, and a new read_own (own-only visibility) - stored in folder_acl.json / folder_owners.json and enforced server-side by ACL::canRead() and ACL::canWrite() across the list, download, zip download, extract, move, copy, rename, create, save, tag-edit, and share-link-creation paths in FileController, the write gate in UploadController, the listing filter in FolderController, and the WebDAV server (src/webdav/*, public/webdav.php). A notable semantic change is that write no longer implies read, so uploaders cannot automatically see other users' files; WebDAV now requires read for full listing and read_own for own-only listing, and writes require write. The patch also adds ACL::applyUserGrantsAtomic(), ACL::purgeUser(), ACL self-healing for folder_acl.json, more robust admin detection, and session/cookie initialization fixes in config/config.php. CPE cpe:2.3:a:filerise:filerise:*:*:*:*:*:*:*:* with the description's explicit 1.4.0 reference places the vulnerable window at the 1.4.x line, with the 1.5.x line supported per the repository's SECURITY.md.

Know when Filerise gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (github) PRIMARY 8.1 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
vuln.today AI 8.1 HIGH

Web/WebDAV-reachable so AV:N, no special timing so AC:L, but a valid low-privilege account is required so PR:L; cross-user read gives C:H and rename/move/write gives I:H, with no availability loss.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (github).

CVSS VectorVendor: github

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

DescriptionCVE.org

FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. In version 1.4.0, a regression allowed folder visibility/ownership to be inferred from folder names. Low-privilege users could see or interact with folders matching their username and, in some cases, other users’ content. This issue has been patched in version 1.5.0, where it introduces explicit per-folder ACLs (owners/read/write/share/read_own) and strict server-side checks across list, read, write, share, rename, copy/move, zip, and WebDAV paths.

Executive ViewAI

Why It Matters

FileRise versions prior to 1.5.0 contain an access-control regression that allows any authenticated user with a basic account to view, modify, share, or relocate folders belonging to other users - including over WebDAV - because the product incorrectly derives ownership from folder names rather than an explicit access-control list. This is most dangerous in multi-tenant or shared-department deployments where sensitive files from many users coexist on the same instance, since it effectively erases the boundary between user workspaces. Leadership should care because a single low-privilege account, which any employee, contractor, or compromised credential could supply, is sufficient to reach and tamper with other people's content, creating confidentiality and integrity exposure.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 79% exploitable
Prevalence
Low
niche self-hosted open-source file manager, limited enterprise footprint
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.

Affected Products (CPE)CVE.org

cpe:2.3:a:filerise:filerise:*:*:*:*:*:*:*:*
CVE-2026-25231 HIGH POC
7.5 Feb 09

Unauthenticated directory traversal in FileRise prior to version 3.3.0 allows remote attackers to read arbitrary files f

CVE-2026-54414 CRITICAL
9.3 Jun 19

Unauthenticated administrator account takeover in FileRise before 3.16.0 is possible via a path traversal flaw in the sh

CVE-2026-25230 MEDIUM POC
4.6 Feb 09

FileRise versions before 3.3.0 contain an HTML injection vulnerability that allows authenticated users to manipulate the

CVE-2025-66403 MEDIUM POC
4.6 Dec 01

FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 2.2.3,

CVE-2026-61843 HIGH
8.2 Oct 14

File overwrite in FileRise prior to 3.18.0 allows an unauthenticated visitor who holds a valid upload-enabled shared-fol

CVE-2026-33072 HIGH
8.2 Mar 20

FileRise, a self-hosted web file manager and WebDAV server, contains a critical hardcoded encryption key vulnerability i

CVE-2026-57490 HIGH
8.1 Oct 14

Multi-factor authentication bypass in FileRise WebDAV prior to 3.16.0 allows an attacker who already holds a valid usern

CVE-2026-33329 HIGH
8.1 Mar 24

FileRise, a self-hosted web file manager and WebDAV server, contains a path traversal vulnerability in its Resumable.js

CVE-2026-104108 HIGH
8.1 Oct 14

Authentication bypass in FileRise versions before 3.23.0 lets a remote attacker log in as an existing local account - in

CVE-2026-103977 HIGH
8.1 Oct 14

Online second-factor guessing against FileRise releases prior to 3.23.0 is permitted well beyond the intended limit beca

CVE-2026-57489 HIGH
8.1 Oct 14

Authentication bypass in FileRise (CWE-290) lets unauthenticated remote attackers impersonate any account - including an

CVE-2025-62509 HIGH
8.1 Oct 20

Low-privilege users of FileRise versions prior to 1.4.0 can view, delete, or modify files owned by other users because t

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy