# CVE-2025-54391: Auth bypass in n/a

> Attackers with valid credentials can bypass Two-Factor Authentication via the EnableTwoFactorAuthRequest SOAP endpoint, gaining unauthorized account access.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2025
- **Updated:** 17 Sep 2025
- **Also known as:** GHSA-34c6-vxrp-m855

## What is CVE-2025-54391?

CVE-2025-54391 is a critical authentication bypass vulnerability in n/a, published on 16 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the EnableTwoFactorAuthRequest SOAP endpoint of Zimbra Collaboration (ZCS) allows an attacker with valid user credentials to bypass Two-Factor Authentication (2FA) protection. The attacker can configure an additional 2FA method (either a third-party authenticator app or email-based 2FA) without presenting a valid authentication token or proving access to an already configured 2FA method. This bypasses 2FA and results in unauthorized access to accounts that are otherwise protected by 2FA.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-54391 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54391 is a critical authentication bypass vulnerability in n/a, published on 16 Sep 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-54391 in the wild and no public exploit code.

Affected product: n/a. 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-54391/ (Markdown: https://insights.sbomify.com/CVE-2025-54391/index.md)
```

## Sources

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

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