# CVE-2025-64523: FileBrowser has Insecure Direct Object Reference (IDOR) in Share Deletion Function > Authenticated users can delete other users' shared links due to missing authorization checks, causing data loss and service disruption. - **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 12 Nov 2025 - **Updated:** 13 Nov 2025 - **Also known as:** GHSA-6cqf-cfhv-659g, GO-2025-4117 ## What is CVE-2025-64523? CVE-2025-64523 is a high-severity missing authorization vulnerability in filebrowser, published on 12 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description File Browser provides a file managing interface within a specified directory and it can be used to upload, delete, preview, rename and edit files. Versions prior to 2.45.1 have 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. Version 2.45.1 contains a fix for the issue. Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-285 (Improper Authorization) ## Which versions are affected by CVE-2025-64523? 4 open source packages ship an affected version, including github.com/filebrowser/filebrowser/v2 and github.com/filebrowser/filebrowser. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.45.1 | | `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.45.1 | | `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.45.1 | | `github.com/filebrowser/filebrowser` | Go | All versions | None | Products: Filebrowser Filebrowser. ## How do I fix CVE-2025-64523? Upgrade github.com/filebrowser/filebrowser/v2 to 2.45.1 or later. ## Is CVE-2025-64523 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64523 exists. ## Other vulnerabilities in filebrowser - [CVE-2026-32760](https://insights.sbomify.com/CVE-2026-32760/): File Browser Self Registration Grants Any User Admin Access When Default Permissions Include Admin (critical 10.0) - [CVE-2026-29188](https://insights.sbomify.com/CVE-2026-29188/): File Browser: TUS Delete Endpoint Bypasses Delete Permission Check (critical 9.1) - [CVE-2023-39612](https://insights.sbomify.com/CVE-2023-39612/): Cross-site scripting in n/a (critical 9.0) - [CVE-2026-30934](https://insights.sbomify.com/CVE-2026-30934/): FileBrowser Quantum: Stored XSS in public share page via unsanitized share metadata (text/template misuse) (high 8.9) - [CVE-2021-46398](https://insights.sbomify.com/CVE-2021-46398/): Cross-Site Request Forgery in Filebrowser (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-64523 and fix it if it is affected. What it is: CVE-2025-64523 is a high-severity missing authorization vulnerability in filebrowser, published on 12 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64523 exists. Affected packages and fixed versions: - github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.45.1 - github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.45.1 - github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.45.1 - github.com/filebrowser/filebrowser (Go): affected all versions; no fix listed 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-64523/ (Markdown: https://insights.sbomify.com/CVE-2025-64523/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-64523 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-64523 - OSV: https://osv.dev/vulnerability/CVE-2025-64523 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-64523/ Summaries are generated and may contain mistakes; the official description above is the record.