dbcve.org
FilebrowserApplication

CVE-2026-32760

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-20
Fix available
A fix is available. Upgrade to 2.62.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In File Browser versions 2.61.2 and below, the signup handler blindly applies all default user permissions—including admin privileges—to newly self-registered accounts without stripping elevated permissions. When self-registration is enabled (signup=true) and default permissions include perm.admin=true, any unauthenticated visitor can create full administrator accounts, gaining complete control over files, users, and server settings.

MitigationUpgrade to File Browser version 2.62.0 or later, which includes a server-side guard that explicitly sets user.Perm.Admin=false for self-registered accounts. Review existing user accounts to identify and remove any unauthorized admin accounts created through this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FilebrowserApplication
Affected:< 2.62.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed File Browser version
    Run the filebrowser --version command or check the binary metadata to determine the installed version number
    Affected if version is below 2.62.0 (any version listed as < 2.62.0)
  2. Verify if self-registration is enabled
    Inspect the File Browser configuration file (commonly settings.json or the main config file) for the signup or registration settings that allow new users to register themselves
    Affected if self-registration or signup functionality is enabled for unauthenticated users
  3. Check default admin permission setting
    Examine the configuration for defaults.perm.admin setting - this controls whether newly created accounts receive administrative privileges by default
    Affected if defaults.perm.admin is set to true in the configuration

A user is affected if they run File Browser version below 2.62.0 with self-registration enabled AND defaults.perm.admin configured as true, allowing any visitor to create administrator accounts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.62.0 or later
Fixed in 2.62.0
Vendor patch github.com →
Interim mitigation

Upgrade to File Browser version 2.62.0 or later, which includes a server-side guard that explicitly sets user.Perm.Admin=false for self-registered accounts. Review existing user accounts to identify and remove any unauthorized admin accounts created through this vulnerability.

Recommended fix High confidence

Filebrowser version 2.62.0 or later

  1. 1. Back up your current Filebrowser configuration and data directory.
  2. 2. Stop the Filebrowser service.
  3. 3. Upgrade Filebrowser to version 2.62.0 or later using your package manager or by downloading the appropriate binary from the official releases.
  4. 4. Start the Filebrowser service.
  5. 5. Verify the upgrade was successful by checking the version.
  6. 6. Review your configuration settings, particularly defaults.perm.admin - ensure it is set to false if self-registration (signup) is enabled.
Caveat Review release notes for any configuration changes between your current version and 2.62.0, as default settings or flags may have changed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Filebrowser Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32760 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32760 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data