Loading...
Skip to main content

CVE-2025-64523 — Vulnerability in...

HIGH

File Browser is Vulnerable to Insecure Direct Object Reference (IDOR) in Share Deletion Function

Published November 13, 2025Updated February 3, 2026Source: osv

Summary

### 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.

Advisory Timeline

  • First published November 13, 2025 (333 days ago).
  • Last revised February 3, 2026 — 82 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Go
Update github.com/filebrowser/filebrowser/v2 to 2.45.1 or later
go get github.com/filebrowser/filebrowser/v2@v2.45.1

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (1)

Affects 1 ecosystem: go (1).

PackageEcosystemAffectedFixed In
github.com/filebrowser/filebrowser/v2
go
All versions2.45.1

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

  • CWE-285
    Improper AuthorizationMITRE
  • CWE-639
    Insecure Direct Object Reference (IDOR)MITRE

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 8.8 score means for each attack dimension.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Frequently Asked Questions

What is CVE-2025-64523?
File Browser is Vulnerable to Insecure Direct Object Reference (IDOR) in Share Deletion Function This vulnerability has been assigned a severity rating of HIGH (CVSS score: 8.8/10).
How do I check if my project is affected by CVE-2025-64523?
CVE-2025-64523 affects github.com/filebrowser/filebrowser/v2. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2025-64523 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
8.8

High exploitability or significant impact. Prioritize remediation within days.

Also Known As

GHSA-6cqf-cfhv-659g
GO-2025-4117

Related CVEs

  • CVE-2026-32760
    CRITICAL

    File Browser Signup Grants Admin When Default Permissions Include Admin

  • CVE-2026-29188
    CRITICAL

    File Browser's TUS Delete Endpoint Bypasses Delete Permission Check

  • CVE-2026-54088
    CRITICAL

    File Browser: Command Injection via Authentication Hook Shell Substitution (Pre-Authentication RCE)

  • CVE-2026-54089
    CRITICAL

    File Browser: Authentication Bypass via Proxy Auth Header Forgery

  • CVE-2026-54096
    HIGH

    File Browser: Improper Access Control Occurs via Pre-Created Public Share for a Non-existent Path

  • CVE-2026-54097
    HIGH

    File Browser: Cross-user unauthorized share-link deletion via unbounded prefix match in DeleteWithPathPrefix

  • CVE-2026-54090
    HIGH

    File Browser has a Command Execution Allowlist Bypass via Shell Metacharacter Injection

  • CVE-2026-55667
    HIGH

    File Browser: Out-of-scope file deletion by a Create-only scoped user via symlink-following RemoveAll in upload failure-cleanup

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies