# CVE-2025-52902: File Browser has Stored Cross-Site Scripting vulnerability

> Attackers can execute arbitrary JavaScript in victims' browsers by uploading malicious Markdown files, potentially leading to session hijacking or data theft.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Jun 2025
- **Updated:** 26 Jun 2025
- **Also known as:** GHSA-4wx8-5gm2-2j97, GO-2025-3784

## What is CVE-2025-52902?

CVE-2025-52902 is a high-severity cross-site scripting vulnerability in filebrowser, published on 26 Jun 2025. Any signed-in user can exploit it over the network, 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. The Markdown preview function of File Browser prior to v2.33.7 is vulnerable to Stored Cross-Site-Scripting (XSS). Any JavaScript code that is part of a Markdown file uploaded by a user will be executed by the browser. Version 2.33.7 contains a fix for the issue.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

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-52902?

Upgrade to a fixed version.

## Is CVE-2025-52902 being exploited?

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

What it is: CVE-2025-52902 is a high-severity cross-site scripting vulnerability in filebrowser, published on 26 Jun 2025. Any signed-in user can exploit it over the network, 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-52902 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-52902/ (Markdown: https://insights.sbomify.com/CVE-2025-52902/index.md)
```

## Sources

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

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