CWE · MITRE source
CWE-289Authentication Bypass by Alternate Name
The product performs authentication based on the name of a resource being accessed, or the name of the actor performing the access, but it does not properly check all possible names for that resource or actor.
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 · 4 mapping(s) from 4 framework(s): OWASP-Web 1 (full) · STIG oracle linux 8 1 (mostly) · ATT&CK 1 (mostly) · STIG rhel 7 1 (partial)
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-2021-34746 | 7.0 | 9.8 | 0.1766 | 2021-09-02 |
CVE-2023-1803 | 7.0 | 9.8 | 0.0076 | 2023-04-14 |
CVE-2024-56511 | 7.0 | 9.8 | 0.2088 | 2025-01-10 |
CVE-2025-29266 | 7.0 | 9.6 | 0.0041 | 2025-03-31 |
CVE-2025-13613 | 7.0 | 9.8 | 0.0042 | 2025-12-10 |
CVE-2025-55130 UPD | 7.0 | 9.1 | 0.0163 | 2026-01-20 |
CVE-2026-24058 | 7.0 | 9.8 | 0.0053 | 2026-01-22 |
CVE-2026-39858 UPD | 7.0 | 10.0 | 0.0048 | 2026-04-30 |
CVE-2026-50627 UPD | 7.0 | 9.1 | 0.0042 | 2026-06-12 |
CVE-2026-53622 | 7.0 | 10.0 | 0.0024 | 2026-06-23 |
CVE-2017-16590 | 5.5 | 8.8 | 0.0340 | 2018-01-23 |
CVE-2023-20046 | 5.5 | 8.8 | 0.0086 | 2023-05-09 |
CVE-2023-3263 | 5.5 | 7.5 | 0.0064 | 2023-08-14 |
CVE-2023-41890 | 5.5 | 7.5 | 0.0060 | 2023-09-19 |
CVE-2024-2098 | 5.5 | 7.5 | 0.0045 | 2024-06-13 |
CVE-2024-51996 | 5.5 | 7.5 | 0.0063 | 2024-11-13 |
CVE-2024-55634 | 5.5 | 8.1 | 0.0040 | 2024-12-10 |
CVE-2024-11283 | 5.5 | 7.5 | 0.0041 | 2025-03-14 |
CVE-2025-41248 | 5.5 | 7.5 | 0.0043 | 2025-09-16 |
CVE-2025-60375 | 5.5 | 7.3 | 0.0027 | 2025-10-09 |
CVE-2025-64343 | 5.5 | 7.8 | 0.0011 | 2025-11-07 |
CVE-2026-44492 UPD | 5.5 | 8.6 | 0.0092 | 2026-06-11 |
CVE-2023-38487 | 3.5 | 6.5 | 0.0066 | 2023-08-04 |
CVE-2023-51663 | 3.5 | 5.3 | 0.0037 | 2023-12-29 |
CVE-2024-34519 | 3.5 | 6.8 | 0.0039 | 2024-05-05 |