# CVE-2025-52996: File Browser's Password Protection of Links Vulnerable to Bypass

> Attackers can bypass password protection on shared links to access files directly, exposing sensitive data to unauthorized users.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 30 Jun 2025
- **Updated:** 4 Aug 2025
- **Also known as:** GHSA-3v48-283x-f2w4, GO-2025-3790

## What is CVE-2025-52996?

CVE-2025-52996 is a low-severity authentication bypass vulnerability in filebrowser, published on 30 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### 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. In versions 2.32.0 and prior, the implementation of password protected links is error-prone, resulting in potential unprotected sharing of a file through a direct download link. This link can either be shared unknowingly by a user or discovered from various locations such as the browser history or the log of a proxy server used. At time of publication, no known patched versions are available.

Weakness: CWE-305 (Authentication Bypass by Primary Weakness)

## Which versions are affected by CVE-2025-52996?

6 open source packages ship an affected version, including github.com/filebrowser/filebrowser and github.com/filebrowser/filebrowser/v2. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/filebrowser/filebrowser` | Go | All versions | None |
| `github.com/filebrowser/filebrowser` | Go | All versions to 1.11.0 | None |
| `github.com/filebrowser/filebrowser` | Go | All versions to 1.11.0 | None |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions | None |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions to 2.42.1 | None |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions to 2.42.1 | None |

Products: Filebrowser Filebrowser.

## How do I fix CVE-2025-52996?

No fix published yet.

## Is CVE-2025-52996 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52996 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-52996 and fix it if it is affected.

What it is: CVE-2025-52996 is a low-severity authentication bypass vulnerability in filebrowser, published on 30 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52996 exists.

Affected packages and fixed versions:
- github.com/filebrowser/filebrowser (Go): affected all versions; no fix listed
- github.com/filebrowser/filebrowser (Go): affected all versions up to 1.11.0; no fix listed
- github.com/filebrowser/filebrowser (Go): affected all versions up to 1.11.0; no fix listed
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; no fix listed
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions up to 2.42.1; no fix listed
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions up to 2.42.1; 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-52996/ (Markdown: https://insights.sbomify.com/CVE-2025-52996/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-52996
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-52996
- OSV: https://osv.dev/vulnerability/CVE-2025-52996

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-52996/
Summaries are generated and may contain mistakes; the official description above is the record.