dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2025-54391

CRITICAL · 9.1 CVSS v3.1 Published 2025-09-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The EnableTwoFactorAuthRequest SOAP endpoint in Zimbra Collaboration fails to validate existing 2FA authentication before allowing configuration of additional 2FA methods. An attacker with valid user credentials can add a new authenticator app or email-based 2FA method without proving access to an already-configured 2FA device, effectively bypassing 2FA protection and gaining full account access.

MitigationApply the vendor-supplied patch for CVE-2025-54391 immediately. Until patched, consider restricting SOAP API access to the EnableTwoFactorAuthRequest endpoint or implementing additional authentication checks before allowing 2FA method configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Zimbra installation and version
    Run 'zmcontrol -v' or 'zmlocalconfig -m product_version' to determine the installed Zimbra Collaboration version
    Affected if The installed version falls within the affected range for CVE-2025-54391 (verify against vendor advisory for specific vulnerable versions)
  2. Confirm 2FA feature is enabled
    Check Zimbra configuration for two-factor authentication settings: 'zmprov gacf | grep -i twofactor' or inspect /opt/zimbra/conf/attrs/attrs.xml for zimbraFeatureTwoFactorAuthEnabled attribute
    Affected if zimbraFeatureTwoFactorAuthEnabled is set to TRUE, indicating 2FA is active on the server
  3. Verify SOAP endpoint accessibility
    Review Zimbra's Jetty or servlet container configuration for the EnableTwoFactorAuthRequest SOAP endpoint (typically exposed via /service/soap/ endpoint)
    Affected if The SOAP endpoint is exposed without additional authentication validation beyond valid user credentials
  4. Check for existing 2FA configuration state
    Query admin account or test user accounts via 'zmprov getAccount user@domain' to inspect zimbraTwoFactorAuthEnabled and zimbraTwoFactorAuthBackupEmailEnabled attributes
    Affected if Users have 2FA enabled but the system permits adding new 2FA methods without prior 2FA verification
  5. Audit recent 2FA-related SOAP requests
    Review Zimbra mailbox.log or audit logs for EnableTwoFactorAuthRequest calls: grep -i 'EnableTwoFactorAuthRequest' /opt/zimbra/log/mailbox.log
    Affected if The endpoint was invoked without prior successful 2FA authentication verification in the session

A Zimbra server is affected if it runs a vulnerable version with 2FA enabled and exposes the EnableTwoFactorAuthRequest SOAP endpoint that permits 2FA method configuration without requiring prior 2FA authentication verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patch for CVE-2025-54391 immediately. Until patched, consider restricting SOAP API access to the EnableTwoFactorAuthRequest endpoint or implementing additional authentication checks before allowing 2FA method configuration.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54391 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54391 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data