CWE · MITRE source
CWE-308Use of Single-factor Authentication
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.
Last updated: 04 July 2026 00:28 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: full · 30 mapping(s) from 4 framework(s): ATT&CK 13 (full) · CAPEC 13 (partial) · ASVS 5.0 3 (mostly) · OWASP-Web 1 (full)
OWASP Top 10 for Web (2025)
This weakness contributes to A07:2025 Authentication Failures.
NIST 800-53 r5 controls that address this weakness (0)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2025-64103 | 7.0 | 9.8 | 0.0034 | 2025-10-29 |
CVE-2023-49075 | 5.5 | 8.4 | 0.0144 | 2023-11-28 |
CVE-2024-47652 | 5.5 | 8.1 | 0.0040 | 2024-10-04 |
CVE-2025-42959 UPD | 5.5 | 8.1 | 0.0049 | 2025-07-08 |
CVE-2026-45749 UPD | 5.5 | 8.1 | 0.0032 | 2026-06-05 |
CVE-2023-34228 | 3.5 | 5.3 | 0.0040 | 2023-05-31 |
CVE-2023-50934 | 3.5 | 5.3 | 0.0044 | 2024-02-02 |
CVE-2023-25681 | 3.5 | 5.3 | 0.0056 | 2024-03-05 |
CVE-2024-50618 | 3.5 | 4.3 | 0.0024 | 2026-02-11 |
CVE-2026-56022 | 3.5 | 5.3 | 0.0031 | 2026-06-18 |
CVE-2026-33550 | 1.5 | 2.0 | 0.0014 | 2026-03-22 |