# CVE-2025-54309: CrushFTP Unprotected Alternate Channel

> Remote attackers can gain admin access via HTTPS when DMZ proxy is disabled, requiring immediate upgrade to secure the FTP server.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 22 Jul 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2025
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-rh5q-v9ww-rqgm

## What is CVE-2025-54309?

CVE-2025-54309 is a critical authentication bypass vulnerability in CrushFTP, published on 18 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CrushFTP 10 before 10.8.5 and 11 before 11.3.4_23, when the DMZ proxy feature is not used, mishandles AS2 validation and consequently allows remote attackers to obtain admin access via HTTPS, as exploited in the wild in July 2025.

Weakness: CWE-420 (Unprotected Alternate Channel)

## Which versions are affected by CVE-2025-54309?

It affects 1 product.


Products: Crushftp Crushftp.

## How do I fix CVE-2025-54309?

No fix has been published for CVE-2025-54309 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 12 Aug 2025.

## Is CVE-2025-54309 being exploited?

Yes. Attackers have exploited CVE-2025-54309 in the wild since at least 22 Jul 2025.

Public exploit code:

- https://github.com/watchtowrlabs/watchTowr-vs-CrushFTP-Authentication-Bypass-CVE-2025-54309 (github_poc): https://github.com/watchtowrlabs/watchTowr-vs-CrushFTP-Authentication-Bypass-CVE-2025-54309
- Exploitation scripts for the CrushFTP CVE-2025-54309: vulnerability (github_poc): https://github.com/foregenix/CVE-2025-54309
- https://github.com/whisperer1290/CVE-2025-54309__Enhanced_exploit (github_poc): https://github.com/whisperer1290/CVE-2025-54309__Enhanced_exploit
- https://github.com/0xLittleSpidy/CVE-2025-54309 (github_poc): https://github.com/0xLittleSpidy/CVE-2025-54309
- CrushFTP AS2 Authentication Bypass (github_poc): https://github.com/blueisbeautiful/CVE-2025-54309
- https://github.com/chin-tech/CrushFTP_CVE-2025-54309 (github_poc): https://github.com/chin-tech/CrushFTP_CVE-2025-54309

## Other vulnerabilities in CrushFTP

- [CVE-2025-31161](https://insights.sbomify.com/CVE-2025-31161/): CrushFTP Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2024-4040](https://insights.sbomify.com/CVE-2024-4040/): CrushFTP VFS Sandbox Escape (critical 9.8, exploited in the wild)
- [CVE-2024-53552](https://insights.sbomify.com/CVE-2024-53552/): Auth bypass in n/a (critical 9.8)
- [CVE-2023-43177](https://insights.sbomify.com/CVE-2023-43177/): Deserialization in n/a (critical 9.8)
- [CVE-2017-14035](https://insights.sbomify.com/CVE-2017-14035/): Deserialization in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-54309 and fix it if it is affected.

What it is: CVE-2025-54309 is a critical authentication bypass vulnerability in CrushFTP, published on 18 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-54309 in the wild since at least 22 Jul 2025.

Affected product: CrushFTP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-54309/ (Markdown: https://insights.sbomify.com/CVE-2025-54309/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-54309
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-54309
- OSV: https://osv.dev/vulnerability/CVE-2025-54309

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-54309/
Summaries are generated and may contain mistakes; the official description above is the record.