CVE-2026-90929
largeAuthorized-User Directory Wipe via Upload Cleanup Bug in File Browser ≤2.63.23
File Browser versions 2.5.0 through 2.63.23 contain an incorrect authorization flaw (CWE-863) in the direct-upload endpoint (resourcePostHandler in http/resource.go). When an authenticated user POSTs an upload with ?override=true targeting an existing directory, the write fails and the error-cleanup path calls Fs.RemoveAll on the request path, recursively deleting the entire directory tree. Because this cleanup bypasses both the Perm.Delete permission check and the checkDescendants rule walk used by the normal delete and patch handlers, a low-privileged user holding only the default Create and Modify permissions can delete directories they are not authorized to remove, including rule-denied files inside them; deletion remains confined to the user's scope. No patched version is currently available, and no public proof of concept or active exploitation is known.
What to do: No patched release exists yet, so audit and constrain access now: remove Create or Modify permissions from any untrusted or shared accounts, and review per-user rules for directories that must not be deletable. Monitor File Browser logs for POST requests with ?override=true aimed at directory paths, and consider a WAF or reverse-proxy rule blocking such requests. Reduce exposure by placing instances behind a VPN or SSO-authenticated proxy, and upgrade as soon as a fixed version above 2.63.23 is released.
| File Browser Project (filebrowser/filebrowser) File Browser | >= 2.5.0, <= 2.63.23 (all versions since v2.5.0; no patched version available) |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
File Browser versions >= 2.5.0 and <= 2.63.23 contain an incorrect authorization flaw in the direct-upload endpoint (resourcePostHandler in http/resource.go). Unlike the TUS upload handler, the direct-upload handler does not reject a target that is an existing directory; a POST with ?override=true aimed at a directory fails inside writeFile (a directory cannot be opened for writing) and the failure-cleanup path then calls Fs.RemoveAll on the request path, recursively deleting the entire tree. This cleanup is gated by neither the Perm.Delete permission nor the checkDescendants rule walk applied by the delete and patch handlers, so an authenticated non-administrator holding only the default Create and Modify permissions can delete directories they are not authorized to delete, including rule-denied files within them. Deletion remains confined to the user's scope because ScopedFs.RemoveAll still enforces the scope guard. The faulty cleanup was introduced in v2.5.0; no patched version is available.
- Weakness
- CWE-863
- Vector
- CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
In the news0 stories
No ingested article mentions this CVE yet.