Summary
File Browser prior to version 2.63.1 fails to re-check a share owner's permissions when public share links are accessed, allowing revoked users' existing links to remain valid.
As a result, files can continue to be downloaded by unauthenticated users via old share URLs even after an administrator has removed the owner's Share and Download permissions.
Affected context
This vulnerability occurs in File Browser deployments using public file sharing where:
- Users can generate public share links for files or directories.
- Administrators later revoke those users' Share and Download permissions.
- Existing share links are not invalidated or re-authorized after permission changes.
The affected code path is the public share download handler, which treats possession of a link as sufficient for access without re-validating the current permissions of the share owner.
Exploit preconditions
- Attack surface: Public HTTP(S) endpoint exposing shared file download links.
- Required access: Any party (authenticated or not) who has or can obtain an existing public share URL created by a user whose permissions are later revoked.
- Trigger point: Performing an HTTP request to the public share download endpoint using a still-valid share link after the share owner's Share/Download permissions have been removed.
- Why exploitation is possible: The download handler authorizes access solely based on the existence and metadata of the share link, without re-checking the owner's current authorization state or enforcing revocation semantics on previously created shares.
Why this happens
The underlying issue is a missing authorization enforcement (CWE-863) in the share download flow: the system does not re-evaluate whether the share owner is still permitted to share or download the underlying resource at the time of access.
Instead, access control is effectively "frozen" at link creation, so permission changes on the account are not propagated to existing shares.
This reflects a design where possession of a link is treated as the only access condition, and authorization logic is not consistently applied on every sensitive operation, particularly in the transition state after administrative revocation.
Potential impact
- Unauthenticated users may continue accessing files through stale public share links after the owner's permissions are revoked.
- Sensitive documents or directories could remain exposed beyond the intended access period.
- Administrative attempts to restrict or remove a user's ability to share files may not take full effect for existing links.
- Compliance or data protection requirements could be violated if access revocation is assumed but not technically enforced.
General mitigation guidance
Mitigation typically focuses on enforcing authorization checks at access time and designing share lifecycles to respect permission changes:
- Ensure that every access via a share link re-validates the share owner's current permissions and the resource's current access policy before serving content.
- Couple share lifecycle with user permissions such that revoking Share/Download capabilities also invalidates or disables existing links belonging to that user.
- Introduce explicit share state management (e.g., active, revoked, expired) and enforce these states in all public and internal handlers.
- Apply least-privilege principles to file sharing features: limit what can be shared publicly, and prefer time-bound or scope-restricted links where possible.
- Provide administrative controls and visibility to list, audit, and centrally revoke all active share links, especially when modifying user roles or permissions.
How teams detect issues like this
Detection can focus on both code-level patterns and behavioral indicators:
- Static analysis / code review:
- Identify handlers for public or token-based access that do not invoke central authorization routines or permission checks.
- Look for logic that authorizes based solely on token existence or share record presence without cross-checking current user or resource permissions.
- Review how permission changes propagate to existing shares and whether there is any refresh or invalidation mechanism.
- Runtime monitoring and logging:
- Log all public share downloads along with user association and timestamps; monitor continued downloads from links associated with accounts whose permissions have changed.
- Create alerts when resources are accessed via public links after administrative actions such as role changes, account suspension, or permission revocation.
- Security testing:
- Incorporate regression tests where a user creates a share, an admin revokes relevant permissions, and tests verify that the share link is no longer usable.
- Use automated security testing tools that specifically target broken access control patterns in public or tokenized endpoints.

