CyberRota Analysis
AI-GeneratedFile Browser versions prior to 2.63.17 are vulnerable to a flaw that allows stale public directory shares to persist after the original directory is deleted, specifically when the deletion path includes a trailing slash. This oversight can lead to unauthorized access to future content if the same directory path is recreated, posing a risk of data exposure. Organizations using affected versions should prioritize updating to the latest release to mitigate this vulnerability.
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
File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. Prior to 2.63.17, File Browser can leave a public directory share behind when the shared directory is deleted through a path with a trailing slash because the share cleanup path calls DeleteWithPathPrefix(file.Path, userID) and the Bolt backend performs the database prefix query with the unnormalized path before trimming the slash for boundary checks, so deleting /a/ does not delete the stored /a share and the stale public share exposes future content if the same path is recreated. This issue is fixed in version 2.63.17.