File Browser exposure is an authentication and path trust problem
File Browser provides a web interface for reading, writing, and sharing files. Its useful feature is also the reason a public instance deserves attention: an authenticated user may be able to browse directories, upload content, or run configured commands. The security question begins with how the instance identifies a user, then continues into which filesystem paths that identity can reach.
The project supports a proxy authentication method. In that mode, an upstream proxy is expected to authenticate the user and pass an identity header. File Browser's documentation says the header value is used by the application, while network configuration determines whether clients can reach the backend directly.…