CWE · MITRE source
CWE-1289Improper Validation of Unsafe Equivalence in Input
The product receives an input value that is used as a resource identifier or other type of reference, but it does not validate or incorrectly validates that the input is equivalent to a potentially-unsafe value.
Attackers can sometimes bypass input validation schemes by finding inputs that appear to be safe, but will be dangerous when processed at a lower layer or by a downstream component. For example, a simple XSS protection mechanism might try to validate that an input has no "<script>" tags using case-sensitive matching, but since HTML is case-insensitive when processed by web browsers, an attacker could inject "<ScrIpT>" and trigger XSS.
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: mostly · 7 mapping(s) from 2 framework(s): ASVS 5.0 6 (mostly) · ATT&CK 1 (partial)
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-2026-33729 | 7.0 | 9.8 | 0.0024 | 2026-03-27 |
CVE-2026-35039 | 7.0 | 9.1 | 0.0021 | 2026-04-06 |
CVE-2025-62718 UPD | 7.0 | 9.9 | 0.0119 | 2026-04-09 |
CVE-2026-39821 UPD | 7.0 | 9.6 | 0.0048 | 2026-05-22 |
CVE-2026-50090 | 7.0 | 9.3 | 0.0025 | 2026-06-12 |
CVE-2024-42219 | 5.5 | 7.8 | 0.0029 | 2024-08-06 |
CVE-2024-45179 | 5.5 | 7.2 | 0.0261 | 2024-10-09 |
CVE-2024-12224 | 5.5 | 8.8 | 0.0019 | 2025-05-30 |
CVE-2026-33496 | 5.5 | 8.1 | 0.0033 | 2026-03-26 |
CVE-2026-33810 UPD | 5.5 | 8.2 | 0.0034 | 2026-04-08 |
CVE-2026-33806 UPD | 5.5 | 7.5 | 0.0041 | 2026-04-15 |
CVE-2026-49942 UPD | 5.5 | 7.3 | 0.0031 | 2026-06-04 |
CVE-2026-42462 | 5.5 | 7.0 | 0.0017 | 2026-06-10 |
CVE-2022-0675 | 3.5 | 5.6 | 0.0090 | 2022-03-02 |
CVE-2024-42218 | 3.5 | 4.7 | 0.0020 | 2024-08-06 |
CVE-2024-45308 | 3.5 | 6.5 | 0.0055 | 2024-09-02 |
CVE-2024-8372 | 3.5 | 4.8 | 0.0057 | 2024-09-09 |
CVE-2026-1094 | 3.5 | 4.6 | 0.0016 | 2026-02-11 |
CVE-2026-27610 UPD | 3.5 | 5.3 | 0.0034 | 2026-02-25 |
CVE-2026-3563 | 3.5 | 5.5 | 0.0034 | 2026-03-17 |
CVE-2026-33515 | 3.5 | 6.5 | 0.0104 | 2026-03-26 |
CVE-2026-22569 | 3.5 | 5.4 | 0.0018 | 2026-03-31 |
CVE-2026-34080 | 3.5 | 5.5 | 0.0018 | 2026-04-07 |
CVE-2026-41239 | 3.5 | 6.8 | 0.0022 | 2026-04-23 |
CVE-2026-41213 | 3.5 | 5.9 | 0.0026 | 2026-04-23 |