# CVE-2021-46398: Cross-Site Request Forgery in Filebrowser

> Attackers can exploit CSRF to create an admin user and execute arbitrary commands via Filebrowser, leading to remote code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 4 Feb 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-72wf-hwcq-65h9, GO-2022-0563

## What is CVE-2021-46398?

CVE-2021-46398 is a high-severity vulnerability in n/a, published on 4 Feb 2022. 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

A Cross-Site Request Forgery vulnerability exists in Filebrowser < 2.18.0 that allows attackers to create a backdoor user with admin privilege and get access to the filesystem via a malicious HTML webpage that is sent to the victim. An admin can run commands using the FileBrowser and hence it leads to RCE.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2021-46398?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.18.0 |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.18.0 |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.18.0 |

Products: Filebrowser Filebrowser.

## How do I fix CVE-2021-46398?

Upgrade github.com/filebrowser/filebrowser/v2 to 2.18.0 or later.

## Is CVE-2021-46398 being exploited?

There is no known exploitation of CVE-2021-46398 in the wild and no public exploit code.

Public exploit code:

- Chamilo LMS v1.11.14 was discovered to contain a zero click code injection vulnerability which allows attackers to execute arbitrary code via a crafted plugin. This vulnerability is triggered through user interaction with the attacker's profile page. (github_poc): https://github.com/febinrev/CVE-2021-46398_Chamilo-LMS-RCE
- FileBrowser 2.17.2 - Cross Site Request Forgery (CSRF) to Remote Code Execution (RCE) (exploitdb)
- A Proof of Concept for the CVE-2021-46398 flaw exploitation  (github_poc): https://github.com/LalieA/CVE-2021-46398

## Other vulnerabilities in n/a

- [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-2026-35604](https://insights.sbomify.com/CVE-2026-35604/): File Browser share links remain accessible after Share/Download permissions are revoked (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-46398 and fix it if it is affected.

What it is: CVE-2021-46398 is a high-severity vulnerability in n/a, published on 4 Feb 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-46398 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.18.0
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.18.0
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.18.0

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

## Sources

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

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