CyberRota Analysis
AI-GeneratedFilebrowser versions up to 2.63.23 are vulnerable due to a failure to remove share records when a shared file is renamed, allowing stale public share links to persist. This can lead to unintended exposure of new files uploaded to the original shared path, as they inherit the previous link's password and expiry settings. Organizations using Filebrowser should prioritize this vulnerability to prevent potential data leaks and unauthorized access to sensitive information.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
filebrowser through 2.63.23 does not remove share records when a shared file is renamed (only deletion triggers share cleanup). The share record is keyed by path, so it survives the rename and remains dormant (returning 404 while the path is empty). When any new, unrelated file later appears at the original shared path — via re-upload, another user with create permission, or a hook — the stale public share link serves that new file under the original link's password and expiry settings, unexpectedly exposing it.