CVE-2025-2825: CrushFTP Authentication Bypass Vulnerability Exploitation (CVE-2025-2825)
The short version: A server side template injection vulnerability in CrushFTP in all versions before 10.7.1 and 11.1.0 on all platforms allows unauthenticated remote attackers to read files from the filesystem outside of the VFS Sandbox, bypass authentication to gain administrative access, and perform remote code execution on the server. BreachRisk discovers exposed instances from your attack surface and flags this finding so you can prioritize by real-world breach risk.
At a glance
| Fact | Detail |
|---|---|
| Our severity take | Critical — BreachRisk score 8.0 (impact 4, likelihood 5) |
| CVSS v3.1 (NVD) | Unknown at time of writing |
| In CISA KEV? | Unknown at time of writing — check the KEV catalog |
| Known exploited? | Unknown at time of writing |
| Requires authenticated session? | Unknown at time of writing |
| CVE | CVE-2025-2825 |
What you need to know
Exposed CrushFTP Server appears vulnerable to authentication bypass vulnerability CVE-2025-2825.
- How they find it — internet-facing exposure of the affected product is discoverable by routine scanning.
- How they use it — attackers exploit the vulnerability against reachable instances.
- What it leads to — compromise of the affected service and, depending on placement, a foothold for further movement.
How serious we see it
Critical — based on BreachRisk impact and likelihood scoring for this threat definition (score 8.0/9). Treat internet-facing instances as priority; confirm exposure and patch status before assuming you're clear.
Recommendations
- Apply security updates to exposed CrushFTP Server.
- Restrict access to vulnerable CrushFTP Server to only trusted IP addresses.
How BreachRisk sees it
BreachRisk discovers internet-facing assets tied to this threat, fingerprints the product where possible, and flags exposure for CVE-2025-2825. Where authorized, it can go beyond detection with a bounded, non-disruptive check rather than leaving you with a maybe. Continuous outside-in coverage means the exposed service is already on your radar ranked by how it actually gets used against you.