Skip to content
OpenAdvisories

Weakness (CWE)

CWE-308: Use of Single-factor Authentication

Base Draft

The product uses an authentication algorithm that uses a single factor (e.g., a password) in a security context that should require more than one factor.

How to prevent it (1 mitigation)
  1. Architecture and Design

    Use multiple independent authentication schemes, which ensures that -- if one of the methods is compromised -- the system itself is still likely safe from compromise. For this reason, if multiple schemes are possible, they should be implemented and required -- especially if they are easy to use.

Source: MITRE CWE-308

11 results · Clear filters · Feed

  • High 7.5
    CVE-2026-19868 Exploited Public exploit

    An authentication enforcement vulnerability in SonicOS SSLVPN service may allow a user with valid credentials for an al…

    KEV Nov 6, 2026
  • High 8.3

    phpMyFAQ before 4.1.9 and 4.2.0-alpha before 4.2.0-beta Missing Current-Password Step-Up on E-mail Change Enables Account Takeover

    phpMyFAQ before 4.1.9 and 4.2.0-alpha before 4.2.0-beta does not require the current password when changing an account e-mail in the user control panel (UserController::updateData, api/user/data/update), checking only the session and CSRF token. An attacker w…

  • High 8.1

    FileRise: WebDAV authentication bypasses TOTP/MFA entirely

    FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.16.0, when an administrator has enabled WebDAV, FileRise WebDAV Basic authentication validates only the account username and password through Au…

  • High 8.1

    Nginx UI: Authentication bypass: password login does not enforce a passkey-only second factor (2FA bypass)

    Nginx UI is a web user interface for the Nginx web server. From 2.0.0 until 2.5.0, POST /api/login checks EnabledOTP but does not require a WebAuthn assertion when EnabledPasskey is true and no TOTP secret is configured. A passkey-only account is therefore is…

  • High 7.1

    phpMyFAQ before 4.1.8 Authentication Bypass via Two-Factor Disable

    phpMyFAQ before 4.1.8 contains an authentication bypass vulnerability in its two-factor authentication (TOTP) disable functionality. The removeTwofactorConfig() handler (reachable via POST /api/user/remove-twofactor) verifies only that the user is logged in a…

  • High 8.1

    OpenEMR 8.2.0 OAuth2 Password Grant Authentication Bypass via SMART Configuration

    OpenEMR through 8.2.0 contains an authentication bypass vulnerability that allows attackers with valid credentials to circumvent multi-factor authentication by exploiting the exposed OAuth2 password grant flow through an unauthenticated client registration en…

  • High 8.1

    Termix's TOTP two-factor authentication can be disabled or bypassed using only the account password

    Termix is a web-based server management platform with SSH terminal, tunneling, and file editing capabilities. The `POST /users/totp/disable` and `POST /users/totp/backup-codes` endpoints in Termix prior to version 2.3.2 accept the account password as a sole a…

  • High 8.7

    Zitadel Bypass Second Authentication Factor

    Starting from 2.53.6, 2.54.3, and 2.55.0, Zitadel only required multi factor authentication in case the login policy has either enabled requireMFA or requireMFAForLocalUsers. If a user has set up MFA without this requirement, Zitadel would consider single fac…

  • High 8.1

    Missing Authentication check after implementation of SAP Security Note 3007182 and 3537476

    An unauthenticated attacker may exploit a scenario where a Hashed Message Authentication Code (HMAC) credential, extracted from a system missing specific security patches, is reused in a replay attack against a different system. Even if the target system is f…

  • High 7.6

    Insecure Authentication Vulnerability

    This vulnerability exists in Shilpi Client Dashboard due to implementation of inadequate authentication mechanism in the login module wherein access to any users account is granted with just their corresponding mobile number. A remote attacker could exploit t…

  • High 8.5

    Pimcore Admin UI has Two Factor Authentication disabled for non admin security firewalls

    The Admin Classic Bundle provides a Backend UI for Pimcore. `AdminBundle\Security\PimcoreUserTwoFactorCondition` introduced in v11 disable the two factor authentication for all non-admin security firewalls. An authenticated user can access the system without …