filebrowser up to 2.33.8 get request method with sensitive query strings
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in filebrowser up to 2.33.8. The impacted element is an unknown function. Executing a manipulation can lead to use of get request method with sensitive query strings. The identification of this vulnerability is CVE-2025-52901. The attack needs to be done within the local network. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability has been found in filebrowser up to 2.33.8 and classified as problematic. This vulnerability affects an unknown part. The manipulation with an unknown input leads to a use of get request method with sensitive query strings vulnerability. The CWE definition for the vulnerability is CWE-598. The web application uses the HTTP GET method to process a request and includes sensitive information in the query string of that request. As an impact it is known to affect confidentiality. CVE summarizes:
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.
The advisory is shared for download at github.com. This vulnerability was named CVE-2025-52901 since 06/20/2025. The exploitation appears to be easy. The attack needs to be done within the local network. Additional levels of successful authentication are needed for exploitation. There are neither technical details nor an exploit publicly available.
Upgrading to version 2.33.9 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-19581). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.5VulDB Meta Temp Score: 4.4
VulDB Base Score: 2.4
VulDB Temp Score: 2.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CNA Base Score: 4.5
CNA Vector (GitHub_M): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Use of get request method with sensitive query stringsCWE: CWE-598
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: filebrowser 2.33.9
Timeline
06/20/2025 🔍06/30/2025 🔍
06/30/2025 🔍
08/04/2025 🔍
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2025-52901 (🔍)
GCVE (CVE): GCVE-0-2025-52901
GCVE (VulDB): GCVE-100-314464
EUVD: 🔍
Entry
Created: 06/30/2025 22:11Updated: 08/04/2025 20:54
Changes: 06/30/2025 22:11 (61), 07/01/2025 02:57 (1), 07/03/2025 18:25 (1), 08/04/2025 20:54 (11)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.