# CVE-2026-30933: FileBrowser Quantum: Password-Protected Share Bypass via /public/api/share/info

> Attackers can bypass password protection on shares to obtain tokenized download URLs, exposing file access tokens.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Mar 2026
- **Updated:** 10 Mar 2026
- **Also known as:** GHSA-525j-95gf-766f, GO-2026-4659

## What is CVE-2026-30933?

CVE-2026-30933 is a high-severity vulnerability in gtsteffaniak filebrowser, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FileBrowser Quantum is a free, self-hosted, web-based file manager. Prior to 1.3.1-beta and 1.2.2-stable, the remediation for CVE-2026-27611 is incomplete. Password protected shares still disclose tokenized downloadURL via /public/api/share/info. This vulnerability is fixed in 1.3.1-beta and 1.2.2-stable.

Weakness: CWE-602 (Client-Side Enforcement of Server-Side Security), CWE-306 (Missing Authentication for Critical Functionality), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-30933?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/gtsteffaniak/filebrowser/backend` | Go | All versions | 0.0.0-20260307130210-09713b32a5f6 |
| `github.com/gtsteffaniak/filebrowser/backend` | Go | All versions | 0.0.0-20260307130210-09713b32a5f6 |
| `github.com/gtsteffaniak/filebrowser/backend` | Go | All versions | 0.0.0-20260307130210-09713b32a5f6 |

Products: Filebrowser Filebrowser.

## How do I fix CVE-2026-30933?

Upgrade github.com/gtsteffaniak/filebrowser/backend to 0.0.0-20260307130210-09713b32a5f6 or later.

## Is CVE-2026-30933 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30933 exists.

## Other vulnerabilities in gtsteffaniak 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-2026-30933 and fix it if it is affected.

What it is: CVE-2026-30933 is a high-severity vulnerability in gtsteffaniak filebrowser, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30933 exists.

Affected packages and fixed versions:
- github.com/gtsteffaniak/filebrowser/backend (Go): affected all versions; fixed in 0.0.0-20260307130210-09713b32a5f6
- github.com/gtsteffaniak/filebrowser/backend (Go): affected all versions; fixed in 0.0.0-20260307130210-09713b32a5f6
- github.com/gtsteffaniak/filebrowser/backend (Go): affected all versions; fixed in 0.0.0-20260307130210-09713b32a5f6

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

## Sources

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

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