# CVE-2025-52900: File Browser has Insecure File Permissions

> Attackers can read uploaded files and the database if the server umask is not hardened, exposing sensitive data to any local OS account.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Jun 2025
- **Updated:** 26 Jun 2025
- **Also known as:** GHSA-jj2r-455p-5gvf, GO-2025-3785

## What is CVE-2025-52900?

CVE-2025-52900 is a medium-severity vulnerability in filebrowser, published on 26 Jun 2025. It can only be exploited from the same machine or local 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. The file access permissions for files uploaded to or created from File Browser are never explicitly set by the application. The same is true for the database used by File Browser. On standard servers using File Browser prior to version 2.33.7 where the umask configuration has not been hardened before, this makes all the stated files readable by any operating system account. Version 2.33.7 fixes the issue.

Weakness: CWE-276 (Incorrect Default Permissions)

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

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 | 2.33.7 |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.33.7 |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.33.7 |

Products: Filebrowser Filebrowser.

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

Upgrade to a fixed version.

## Is CVE-2025-52900 being exploited?

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

What it is: CVE-2025-52900 is a medium-severity vulnerability in filebrowser, published on 26 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52900 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; fixed in 2.33.7
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.33.7
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.33.7

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-52900/ (Markdown: https://insights.sbomify.com/CVE-2025-52900/index.md)
```

## Sources

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

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