/

CVE-2026-30933

Severity:

HIGH RISK

(7.5)

Information Exposure / Incomplete Authentication

CVE-2026-30933

Analyzed

Vulnerability type

Category:

Information Exposure / Incomplete Authentication

CWE:

CWE-200, CWE-306, CWE-602

Impact:

Unauthorized Access to Protected File Shares

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

FileBrowser Quantum fails to fully protect sensitive share metadata for password-protected shares, exposing a tokenized downloadURL through the /public/api/share/info endpoint.

Under certain conditions, an unauthenticated or insufficiently authenticated party can retrieve this tokenized URL and potentially download shared files without knowing the share password.

Affected context

This vulnerability appears in FileBrowser Quantum deployments that expose the /public/api/share/info endpoint for link-based file sharing.

It specifically affects password-protected shares where:

  • The front-end or external client can query share information via the public API
  • The backend returns tokenized downloadURL values even when the share is configured to require a password
  • Access control checks do not consistently gate all share-related metadata behind successful authentication

Exploit preconditions

  • Attack surface: Public or semi-public HTTP(S) interface of a FileBrowser Quantum instance.
  • Required access: Network access to the FileBrowser Quantum web API; no valid share password is strictly required if the endpoint is reachable and insufficiently protected.
  • Trigger point: Calling /public/api/share/info (or logically equivalent endpoints) for a password-protected share.
  • Why exploitation is possible: The application exposes sensitive tokenized downloadURL data via the info endpoint without enforcing complete authentication/authorization, causing information exposure of a value that acts as a bearer token for file downloads.

Why this happens

The root cause is an incomplete enforcement of authentication and authorization when serving metadata for password-protected shares.

While the application intends to guard access with a password, the backend still returns a tokenized downloadURL in share info responses even when the caller has not proved knowledge of the password.

This behavior maps to:

  • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, because a security-sensitive token (download URL) is exposed.
  • CWE-306: Missing Authentication for Critical Function, as the effective download capability is granted without full authentication.
  • CWE-602: Client-Side Enforcement of Security, since the server seems to rely partly on the client to respect share protections rather than enforcing them strictly on the server side.

Potential impact

  • Unauthorized download of files from password-protected shares via exposed tokenized URLs
  • Bypass of intended password protection on shared resources
  • Exposure of potentially sensitive or confidential documents stored in FileBrowser Quantum
  • Increased risk of data exfiltration if shared links are widely distributed or guessable

General mitigation guidance

Effective mitigation focuses on treating share tokens and related URLs as sensitive secrets and enforcing access control entirely on the server side.

Useful patterns include:

  • Ensuring that all endpoints exposing share information verify authentication and authorization before returning any tokenized URLs or equivalent bearer tokens.
  • Segregating public and protected metadata so that share info accessible without authentication never includes direct download URLs or tokens.
  • Implementing strict server-side checks that validate share passwords (or other credentials) before allowing any action that could lead to file retrieval.
  • Designing tokenized URLs as short-lived, tightly scoped, and revocable, reducing the impact of exposure.
  • Avoiding reliance on client-side logic (such as front-end checks) to restrict access to protected shares.

How teams detect issues like this

Organizations can detect similar issues by:

  • API review: Inspecting REST or GraphQL endpoints that return link, token, or URL fields, and verifying whether they are consistently gated by authentication and authorization checks.
  • Static analysis: Searching for code paths that serialize share objects or download tokens into API responses without preceding access-control checks.
  • Security testing: Performing authenticated and unauthenticated probing of public endpoints to see if password-protected share metadata, including tokenized URLs, is exposed.
  • Policy enforcement: Defining coding guidelines that prohibit returning direct download tokens or URLs from "info" endpoints unless the request is fully authenticated and authorized, and using automated tools to flag violations during code review.

Sources

SourceLink
github.comgithub.com/gtsteffaniak/filebrowser/releases/tag/v1.2.2-stable
github.comgithub.com/gtsteffaniak/filebrowser/releases/tag/v1.3.1-beta
github.comgithub.com/gtsteffaniak/filebrowser/security/advisories/GHSA-525j-95gf-766f

Frequently asked

questions

Exploitability depends on how widely the FileBrowser Quantum interface is exposed. If the /public/api/share/info endpoint is reachable over the internet or a large internal network, an attacker with network access can attempt to query information about password-protected shares.

In the vulnerable design, the attacker does not necessarily need the share password if the endpoint returns the tokenized downloadURL without verifying it. They only need network access and the ability to call the relevant public API endpoint.

The safest approach is to enforce strict server-side authentication and authorization before returning any sensitive share metadata, especially download tokens or URLs. Password validation or equivalent authentication must occur before exposing any data that can be used to access the shared files.

Treat share tokens, signed URLs, and similar artifacts as sensitive credentials, enforce access control on the server for every endpoint that exposes them, avoid client-side-only protections, and incorporate security-focused API reviews and automated checks into the development lifecycle.

Find out what's already
exploitable in your codebase.