# CVE-2025-3871: Broken Access Control Leads to Limited Denial of Service in GoAnywhere MFT 7.8.0 and earlier

> An attacker can disable users by exploiting broken access control in GoAnywhere MFT when GOTP 2FA is enabled and email is missing.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2025
- **Updated:** 18 Jul 2025
- **Also known as:** GHSA-p75j-78r4-rcp2

## What is CVE-2025-3871?

CVE-2025-3871 is a medium-severity missing authorization vulnerability in Fortra GoAnywhere MFT, published on 16 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Broken access control in Fortra's GoAnywhere MFT prior to 7.8.1 allows an attacker to create a denial of service situation when configured to use GoAnywhere One-Time Password (GOTP) email two-factor authentication (2FA) and the user has not set an email address. In this scenario, the attacker may enter the email address of a known user when prompted and the user will be disabled if that user has configured GOTP.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-3871 being exploited?

There is no known exploitation of CVE-2025-3871 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3871 is a medium-severity missing authorization vulnerability in Fortra GoAnywhere MFT, published on 16 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3871 in the wild and no public exploit code.

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-2025-3871/ (Markdown: https://insights.sbomify.com/CVE-2025-3871/index.md)
```

## Sources

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

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