dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-3091

HIGH · 7.5 CVSS v3.1 Published 2025-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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
An low privileged remote attacker in possession of the second factor for another user can login as that user without knowledge of the other user`s password.

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

This is an authentication bypass vulnerability where a low-privileged remote attacker who possesses another user's second factor (e.g., TOTP code, SMS token) can successfully authenticate as that target user without knowing the target user's password. The flaw appears to be in the authentication logic where second-factor verification is incorrectly allowing full authentication without password validation.

MitigationFix the authentication flow to ensure that password verification is always required as the first factor before or alongside second-factor validation, regardless of whether a valid second-factor token is presented.

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 the affected application and version
    Locate the application version through its standard interface (admin panel, about page, or by running 'version' command via CLI if available). Check vendor security advisories for CVE-2025-3091 to obtain the specific affected version ranges.
    Affected if The installed version falls within the affected version range published for this CVE.
  2. Verify second-factor authentication configuration
    Access the authentication or security settings panel in the application. Locate the multi-factor authentication (MFA/2FA) configuration section. Confirm that TOTP, SMS, or other second-factor methods are enabled for user accounts.
    Affected if Second-factor authentication is enabled and the application handles authentication through the vulnerable code path.
  3. Test authentication flow with second-factor only
    In an isolated test environment, attempt to authenticate using a valid second-factor token (TOTP code or SMS token) without providing the user's password. Observe whether the authentication attempt succeeds.
    Affected if Authentication succeeds using only a valid second-factor token without password validation, indicating the bypass is present.
  4. Review authentication logs for bypass patterns
    Export or view authentication logs from the application or associated identity provider. Search for successful login events that lack password verification records or show second-factor validation without preceding password check.
    Affected if Logs show successful authentications where second-factor was validated but password verification was not performed or recorded.
  5. Inspect authentication module configuration files
    If accessible, examine the authentication configuration files (such as auth.conf, security.xml, or similar) for the authentication chain or pipeline settings. Look for settings controlling the order of password versus second-factor validation.
    Affected if Configuration shows second-factor validation can proceed independently of password validation, or the authentication chain lacks enforcement of password-first validation.

You are affected if your installed version matches the affected range AND second-factor authentication is enabled, particularly if testing confirms passwordless authentication via second-factor alone is possible.

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

Fix the authentication flow to ensure that password verification is always required as the first factor before or alongside second-factor validation, regardless of whether a valid second-factor token is presented.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3091 — 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-3091 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