CVE-2025-52901

What it is

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.

At a glance

Exploitability

Can be exploited from the same network segment with an admin-level account. High risk of data exposure.

Exploit odds

0.5% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2025-06-30 20:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 09:37 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.5% in the next 30 days (EPSS).
• Severity: 4.5 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2025-06-30 20:15 UTC

Last modified

2026-06-17 09:37 UTC

Exploit probability

0.5% · EPSS, next 30 days

Weakness

CWE-598

Record status

Modified

Affected

• Filebrowser ≤ 2.33.0

Attack profile CVSS 3.1 · 4.5

Attack vector

Adjacent network

Complexity

Low

Privileges needed

High

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2025-52901.md and follow it. Check whether this project is affected by CVE-2025-52901. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge