CVE-2025-52901 Details
Description
File Browser provides a file managing interface within a specified directory and it can be used to upload, delete, preview, rename and edit files. Prior to version 2.33.9, access tokens are used as GET parameters. The JSON Web Token (JWT) which is used as a session identifier will get leaked to anyone having access to the URLs accessed by the user. This will give an attacker full access to a user's account and, in consequence, to all sensitive files the user has access to. This issue has been patched in version 2.33.9.
A vulnerability in File Browser prior to version 2.33.9 allows access tokens to be transmitted as GET parameters, leading to the unintentional exposure of JSON Web Tokens (JWTs) used for session identification. This leakage can occur through various channels such as browser history, web server access logs, and HTTP referrer headers, potentially granting attackers full access to a user's account and sensitive files. The issue has been addressed in version 2.33.9.
Users can update to File Browser version 2.33.9 or later, where this vulnerability has been fixed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jun 30, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-598 | Use of GET Request Method With Sensitive Query Strings | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| filebrowser filebrowser | <= 2.33.0 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Aug 4, 2025 | CVE Modified | [email protected] |
| Jul 10, 2025 | Initial Analysis | [email protected] |
| Jun 30, 2025 | New CVE Received | [email protected] |