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: 09 May 2026 03:25 UTC
NIST 800-53 r5 controls that address this weakness (0)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2026-33729 | 2.0 | 9.8 | 0.0002 | 2026-03-27 |
CVE-2024-12224 | 1.8 | 8.8 | 0.0015 | 2025-05-30 |
CVE-2026-35039 | 1.8 | 9.1 | 0.0002 | 2026-04-06 |
CVE-2024-42219 | 1.6 | 7.8 | 0.0015 | 2024-08-06 |
CVE-2026-33496 | 1.6 | 8.1 | 0.0018 | 2026-03-26 |
CVE-2024-45179 | 1.5 | 7.2 | 0.0122 | 2024-10-09 |
CVE-2026-41239 | 1.4 | 6.8 | 0.0005 | 2026-04-23 |
CVE-2024-45308 | 1.3 | 6.5 | 0.0014 | 2024-09-02 |
CVE-2026-33515 | 1.3 | 6.5 | 0.0014 | 2026-03-26 |
CVE-2022-0675 | 1.2 | 5.6 | 0.0053 | 2022-03-02 |
CVE-2026-41213 | 1.2 | 5.9 | 0.0006 | 2026-04-23 |
CVE-2026-27610 | 1.1 | 5.3 | 0.0002 | 2026-02-25 |
CVE-2026-3563 | 1.1 | 5.5 | 0.0003 | 2026-03-17 |
CVE-2026-22569 | 1.1 | 5.4 | 0.0009 | 2026-03-31 |
CVE-2026-34080 | 1.1 | 5.5 | 0.0001 | 2026-04-07 |
CVE-2024-8372 | 1.0 | 4.8 | 0.0002 | 2024-09-09 |
CVE-2024-42218 | 0.9 | 4.7 | 0.0001 | 2024-08-06 |
CVE-2026-1094 | 0.9 | 4.6 | 0.0002 | 2026-02-11 |
CVE-2026-39972 | 0.0 | 0.0 | 0.0009 | 2026-04-09 |