Account hijacking via session tokens in URLs
Published Jun 30, 2025 · Updated Aug 4, 2025
Sensitive data exposure in File Browser before 2.33.9 allows attackers with URL access to hijack user sessions and read files. The frontend appends the session JWT as the auth query parameter when opening raw-file downloads and command WebSockets, placing it in browser history, server and proxy logs, and referrer headers. Access to any such URL record is required; the stolen token grants the affected user's account access and exposes every file available to that account.
Summary
What happened
Sensitive data exposure in File Browser before 2.33.9 allows attackers with URL access to hijack user sessions and read files. The frontend appends the session JWT as the auth query parameter when opening raw-file downloads and command WebSockets, placing it in browser history, server and proxy logs, and referrer headers. Access to any such URL record is required; the stolen token grants the affected user's account access and exposes every file available to that account.
The record
- CVE
- CVE-2025-52901
- Published
- Jun 30, 2025
- Updated
- Aug 4, 2025
- Vendor
- File Browser
- Product
- File Browser
- Classifications
- CWE-598, T1550.004
- Attack vector
- adjacent
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 30, 2025CVE publishedPublication date reported by the CVE source.
- Aug 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.33.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- JWT query-string exposure proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo