---
title: "CWE-308: Use of Single-factor Authentication"
url: https://radicalnotion.ai/cwe/cwe-308
type: cwe
description: "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."
updated: 2026-11-10
source: RadicalNotion.AI
license: CC BY-NC 4.0 (https://creativecommons.org/licenses/by-nc/4.0/)
---

# CWE-308: Use of Single-factor Authentication

- **Abstraction:** Base
- **Structure:** Simple
- **Status:** Draft
- **Likelihood of exploit:** High
- **CVEs with this as primary weakness:** 23
- **Of those, in CISA KEV:** 1
- **New in 2026:** 16
- **CWE catalog version:** 4.21

## Description

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.

## Modes of introduction

| Phase | Note |
| --- | --- |
| Architecture and Design | COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic. |

## Common consequences

| Scope | Impact | Note |
| --- | --- | --- |
| Access Control | Bypass Protection Mechanism | If the secret in a single-factor authentication scheme gets compromised, full authentication is possible. |

## Potential mitigations

### 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.

## Demonstrative examples

### Example 1

In both of these examples, a user is logged in if their given password matches a stored password:

Bad code:

```c
unsigned char *check_passwd(char *plaintext) {
    ctext = simple_digest("sha1",plaintext,strlen(plaintext), ... );
    //Login if hash matches stored hash
    if (equal(ctext, secret_password())) {
        login_user();
    }
}
```

Bad code:

```java
String plainText = new String(plainTextIn);
MessageDigest encer = MessageDigest.getInstance("SHA");
encer.update(plainTextIn);
byte[] digest = password.digest();
//Login if hash matches stored hash
if (equal(digest,secret_password())) {
    login_user();
}
```

This code relies exclusively on a password mechanism (CWE-309) using only one factor of authentication (CWE-308). If an attacker can steal or guess a user's password, they are given full access to their account. Note this code also uses SHA-1, which is a weak hash (CWE-328). It also does not use a salt (CWE-759).

## Observed examples

| CVE | Description |
| --- | --- |
| CVE-2022-35248 | Chat application skips validation when Central Authentication Service (CAS) is enabled, effectively removing the second factor from two-factor authentication |

## Real CVEs with this weakness (sample of 12 of 23)

| CVE | Title | Severity | CVSS | EPSS | CISA KEV | Published |
| --- | --- | --- | --- | --- | --- | --- |
| CVE-2026-19868 | SonicWall SonicOS SSLVPN Use of Single-factor Authentication Vulnerability | high | 7.5 | - | Yes | 2026-11-06 |
| CVE-2026-58240 | Missing Authentication check in SAP NetWeaver (Message Server) | critical | 9.8 | - | No | 2026-09-08 |
| CVE-2026-15616 | Local MFA not enforced during SSO sign-in | critical | 9.1 | - | No | 2026-07-23 |
| CVE-2026-111884 | 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 | high | 8.7 | - | No | 2026-10-17 |
| CVE-2025-64103 | Zitadel Bypass Second Authentication Factor | high | 8.7 | - | No | 2025-10-29 |
| CVE-2026-67611 | OpenEMR 8.2.0 OAuth2 Password Grant Authentication Bypass via SMART Configuration | high | 8.6 | - | No | 2026-08-03 |
| CVE-2023-49075 | Pimcore Admin UI has Two Factor Authentication disabled for non admin security firewalls | high | 8.5 | - | No | 2023-11-28 |
| CVE-2026-57490 | FileRise: WebDAV authentication bypasses TOTP/MFA entirely | high | 8.1 | - | No | 2026-10-14 |
| CVE-2026-45749 | Termix's TOTP two-factor authentication can be disabled or bypassed using only the account password | high | 8.1 | - | No | 2026-06-05 |
| CVE-2025-42959 | Missing Authentication check after implementation of SAP Security Note 3007182 and 3537476 | high | 8.1 | - | No | 2025-07-08 |
| CVE-2024-47652 | Insecure Authentication Vulnerability | high | 7.6 | - | No | 2024-10-04 |
| CVE-2026-111552 | Multi-Factor Authentication Bypass in Hyper Technology's Hyper E-Commerce Infrastructure | high | 7.1 | - | No | 2026-11-12 |

## Related attack patterns (CAPEC)

- [CAPEC-16](https://radicalnotion.ai/capec/capec-16): Dictionary-based Password Attack
- [CAPEC-49](https://radicalnotion.ai/capec/capec-49): Password Brute Forcing
- [CAPEC-509](https://radicalnotion.ai/capec/capec-509): Kerberoasting
- [CAPEC-55](https://radicalnotion.ai/capec/capec-55): Rainbow Table Password Cracking
- [CAPEC-555](https://radicalnotion.ai/capec/capec-555): Remote Services with Stolen Credentials
- [CAPEC-560](https://radicalnotion.ai/capec/capec-560): Use of Known Domain Credentials
- [CAPEC-561](https://radicalnotion.ai/capec/capec-561): Windows Admin Shares with Stolen Credentials
- [CAPEC-565](https://radicalnotion.ai/capec/capec-565): Password Spraying
- [CAPEC-600](https://radicalnotion.ai/capec/capec-600): Credential Stuffing
- [CAPEC-644](https://radicalnotion.ai/capec/capec-644): Use of Captured Hashes (Pass The Hash)
- [CAPEC-645](https://radicalnotion.ai/capec/capec-645): Use of Captured Tickets (Pass The Ticket)
- [CAPEC-652](https://radicalnotion.ai/capec/capec-652): Use of Known Kerberos Credentials
- [CAPEC-653](https://radicalnotion.ai/capec/capec-653): Use of Known Operating System Credentials
- [CAPEC-70](https://radicalnotion.ai/capec/capec-70): Try Common or Default Usernames and Passwords

## Related weaknesses

| Relationship | CWE | Name |
| --- | --- | --- |
| Parent | [CWE-654](https://radicalnotion.ai/cwe/cwe-654) | Reliance on a Single Factor in a Security Decision |
| Parent | [CWE-1390](https://radicalnotion.ai/cwe/cwe-1390) | Weak Authentication |
| Peer | [CWE-309](https://radicalnotion.ai/cwe/cwe-309) | Use of Password System for Primary Authentication |

## Taxonomy mappings

| Taxonomy | Entry | Id | Fit |
| --- | --- | --- | --- |
| CLASP | Using single-factor authentication | - | - |

## Frequently asked questions

### What is CWE-308?

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.

### What CVEs are caused by CWE-308?

23 recorded CVEs are attributed to CWE-308, including CVE-2026-19868, CVE-2026-58240 and CVE-2026-15616. 1 is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog.

### How do you prevent CWE-308?

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.

### What are the consequences of CWE-308?

Exploiting CWE-308 can lead to: Bypass Protection Mechanism.

### Is CWE-308 actively exploited?

Yes. 1 CWE-308 vulnerability is in CISA's KEV catalog of actively exploited flaws, out of 23 recorded CVEs.

Primary source: [MITRE CWE](https://cwe.mitre.org/data/definitions/308.html)

---

Source: [RadicalNotion.AI](https://radicalnotion.ai/cwe/cwe-308). Licensed CC BY-NC 4.0; attribute RadicalNotion.AI and link the source page when you reuse this data.
