Summary
FileRise, a self-hosted web file manager and WebDAV server, allows unauthenticated users to read files stored under the /uploads directory in versions prior to 3.3.0.
Because access control is not enforced on this directory, any user who can guess or discover a file path may retrieve potentially sensitive data without authentication.
Affected context
This vulnerability affects FileRise instances (pre-3.3.0) that expose the /uploads directory over HTTP/WebDAV without a protective access control layer.
It is most relevant when users upload files that they assume are private or require authentication to access.
Environments with predictable naming schemes, shared links, or directory listings are at higher risk, but even without those, path guessing or information leakage from logs and references can make access possible.
Exploit preconditions
- Attack surface: Publicly reachable HTTP/WebDAV endpoints of the FileRise instance
- Required access: Network access to the FileRise server (no prior authentication needed)
- Trigger point: Direct HTTP/WebDAV requests to paths under
/uploads(e.g.,/uploads/<filename>) - Why exploitation is possible: The application fails to enforce authentication and authorization checks on the
/uploadsdirectory, treating uploaded content as publicly readable resources rather than protected assets.
Why this happens
The core issue is a missing authorization control on a sensitive directory, matching CWE-284: Improper Access Control and CWE-552: Files or Directories Accessible to External Parties.
The design or configuration allows any HTTP client to fetch files from /uploads without verifying the user's identity or permissions.
Abstractly, this reflects an insecure pattern where user-generated or sensitive content is stored in a web-accessible location but is not bound to any access-control policy at retrieval time.
Potential impact
- Exposure of sensitive or private documents uploaded by users
- Leakage of personally identifiable information (PII) or business-confidential data
- Disclosure of temporary files that may contain tokens, configuration fragments, or diagnostic information
- Privacy violations and potential regulatory compliance issues (e.g., data protection obligations)
- Information disclosure that could aid further attacks (e.g., reconnaissance for phishing or social engineering)
General mitigation guidance
Effective mitigation typically focuses on enforcing robust access control around uploaded content and reducing direct exposure of storage paths:
- Apply authentication and authorization checks before serving any file under upload directories.
- Use non-web-accessible storage locations for uploaded files, serving them through controlled application handlers instead of direct static file access.
- Associate uploads with an owning user or group and verify permissions on every file retrieval request.
- Use unpredictable file identifiers or randomised paths in addition to access control to reduce the impact of path guessing.
- Limit the sensitivity of data stored in publicly reachable directories, and clearly document which paths are intended to be public.
How teams detect issues like this
Detection can leverage both code-level and runtime signals:
- Static analysis / code review:
- Flag routes or middleware that map
/uploads(or similar) directly to the filesystem without authorization checks. - Identify use of static file serving mechanisms that bypass authentication logic.
- Review configuration files (e.g., for reverse proxies or web servers) that expose upload paths as public directories.
- Dynamic / operational monitoring:
- Monitor access logs for repeated requests to
/uploadspaths, especially from unknown or unauthenticated clients. - Use web application scanners configured to probe common upload directories for accessible content.
- Automated security testing tools, including DAST and SAST, can be integrated into CI/CD to surface unauthenticated file-access paths systematically.

