# CVE-2024-0204: Authentication Bypass in GoAnywhere MFT

> An attacker can bypass authentication to create an admin user in GoAnywhere MFT, leading to full system compromise.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2024
- **Updated:** 30 May 2025
- **Also known as:** GHSA-f8xf-39w2-mrc6

## What is CVE-2024-0204?

CVE-2024-0204 is a critical authentication bypass vulnerability in Fortra GoAnywhere MFT, published on 22 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Authentication bypass in Fortra's GoAnywhere MFT prior to 7.4.1 allows an unauthorized user to create an admin user via the administration portal.

Weakness: CWE-425 (Direct Request)

## Which versions are affected by CVE-2024-0204?

It affects 1 product.


Products: Fortra Goanywhere Managed File Transfer.

## How do I fix CVE-2024-0204?

No fix has been published for CVE-2024-0204 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-0204 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-0204 exists.

Public exploit code:

- Authentication Bypass in GoAnywhere MFT (github_poc): https://github.com/horizon3ai/CVE-2024-0204
- Scanning for vulnerable GoAnywhere MFT CVE-2024-0204 (github_poc): https://github.com/cbeek-r7/CVE-2024-0204
- This script exploits the CVE-2024-0204 vulnerability in Fortra GoAnywhere MFT, allowing the creation of unauthorized administrative users, for educational and authorized testing purposes. (github_poc): https://github.com/m-cetin/CVE-2024-0204
- Fortra GoAnywhere MFT Unauthenticated Remote Code Execution (metasploit)
- Fortra GoAnywhere MFT 7.4.1 - Authentication Bypass (exploitdb)
- Fortra GoAnywhere MFT - Authentication Bypass (nuclei): http/cves/2024/CVE-2024-0204.yaml

## Other vulnerabilities in Fortra GoAnywhere MFT

- [CVE-2025-10035](https://insights.sbomify.com/CVE-2025-10035/): Fortra GoAnywhere MFT Deserialization of Untrusted Data (critical 10.0, exploited in the wild)
- [CVE-2023-0669](https://insights.sbomify.com/CVE-2023-0669/): Fortra GoAnywhere MFT Remote Code Execution (high 7.2, exploited in the wild)
- [CVE-2025-14362](https://insights.sbomify.com/CVE-2025-14362/): GoAnywhere MFT SFTP Service Login Vulnerable to Brute Force Attack Under Certain Circumstances (high 7.3)
- [CVE-2026-1089](https://insights.sbomify.com/CVE-2026-1089/): User‑Controlled HTTP Header In Fortra's GoAnywhere MFT Allows Arbitrary DNS Lookups (medium 6.5)
- [CVE-2024-25157](https://insights.sbomify.com/CVE-2024-25157/): Authentication bypass in GoAnywhere MFT prior to 7.6.0 (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-0204 and fix it if it is affected.

What it is: CVE-2024-0204 is a critical authentication bypass vulnerability in Fortra GoAnywhere MFT, published on 22 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-0204 exists.

Affected product: Fortra GoAnywhere MFT. 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-2024-0204/ (Markdown: https://insights.sbomify.com/CVE-2024-0204/index.md)
```

## Sources

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

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