GitHub Advisoryadvisory · Go

GHSA-6cqf-cfhv-659g File Browser is Vulnerable to Insecure Direct Object Reference (IDOR) in Share Deletion Function

HIGH Published 2025-11-13 Modified 2026-02-03 Official page ↗
Aliases
CVE-2025-64523
Ecosystem
Go
Packages
github.com/filebrowser/filebrowser/v2
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weaknesses
CWE-285, CWE-639
Reviewed
2025-11-13

Affected packages

• Go github.com/filebrowser/filebrowser/v2: < 2.45.1 → fixed in 2.45.1

Description

Summary It has been found an Insecure Direct Object Reference (IDOR) vulnerability in the FileBrowser application's share deletion functionality. This vulnerability allows any authenticated user with share permissions to delete other users' shared links without authorization checks. The impact is significant as malicious actors can disrupt business operations by systematically removing shared files and links. This leads to denial of service for legitimate users, potential data loss in collaborative environments, and breach of data confidentiality agreements. In organizational settings, this could affect critical file sharing for projects, presentations, or document collaboration. Details Technical Analysis The vulnerability exists in` /http/share.go` at lines 72-82. The shareDeleteHandler function processes deletion requests using only the share hash without comparing the link.UserID with the current authenticated user's ID (d.user.ID). This missing authorization check enables the vulnerability. ``` var shareDeleteHandler = withPermShare(func(_ http.ResponseWriter, r *http.Request, d *data) (int, error) { hash := strings.TrimSuffix(r.URL.Path, "/") hash = strings.TrimPrefix(hash, "/") if hash == "" { return http.StatusBadRequest, nil } err := d.store.Share.Delete(hash) // Missing ownership validation return errToStatus(err), err }) ``` PoC Reproduce Steps: Prerequisites: Two authenticated user accounts (User A and User B) with share permissions Step 1: User A creates a share link and obtains the share hash (e.g., MEEuZK-v) Step 2: User B authenticates and obtains a valid JWT token Step 3: User B sends DELETE request to /api/share/MEEuZK-v with their own JWT token Step 4: Observe that User A's share is deleted without authorization DELETE /api/share/MEEuZK-v HTTP/1.1 Host: filebrowser.local Content-Type: application/json Impact The impact is significant as malicious actors can disrupt business operations by systematically removing shared files and links. This leads to denial of service for legitimate users, potential data loss in collaborative environments, and breach of data confidentiality agreements. In organizational settings, this could affect critical file sharing for projects, presentations, or document collaboration.

Related

Alias · CVE (1)

  • CVE-2025-64523 File Browser provides a file managing interface within a specified directory and it can be used to upload, delete, preview, rename and edit… vulnerability

Weakness · CWE (2)

  • CWE-285 Improper Authorization weakness
  • CWE-639 Authorization Bypass Through User-Controlled Key weakness

References