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: 14 October 2026 20:41 UTC
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
—
—
V5.2.2V9.1.3V10.4.6V2.2.2
NIST 800-53 r5 controls PROPOSED for this weakness (0)AI-assisted
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| 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-48710 KEV UPD | 7.8 | 6.5 | 0.0706 | 2026-05-26 |
CVE-2025-62718 UPD | 7.3 | 9.9 | 0.0119 | 2026-04-09 |
CVE-2026-33729 UPD | 7.2 | 9.8 | 0.0031 | 2026-03-27 |
CVE-2026-89049 | 7.0 | 9.9 | 0.0066 | 2026-09-10 |
CVE-2026-39821 UPD | 6.9 | 9.6 | 0.0069 | 2026-05-22 |
CVE-2026-97196 | 6.8 | 9.1 | 0.0030 | 2026-09-30 |
CVE-2026-35039 UPD | 6.7 | 9.1 | 0.0022 | 2026-04-06 |
CVE-2026-50090 UPD | 6.5 | 9.3 | 0.0037 | 2026-06-12 |
CVE-2024-12224 UPD | 6.4 | 8.8 | 0.0022 | 2025-05-30 |
CVE-2026-86831 | 6.3 | 8.7 | 0.0064 | 2026-09-16 |
CVE-2026-33810 UPD | 6.2 | 8.2 | 0.0034 | 2026-04-08 |
CVE-2026-33496 UPD | 6.1 | 8.1 | 0.0051 | 2026-03-26 |
CVE-2026-100255 | 6.1 | 8.1 | 0.0035 | 2026-09-30 |
CVE-2024-45179 UPD | 5.9 | 7.2 | 0.0260 | 2024-10-09 |
CVE-2026-33806 UPD | 5.9 | 7.5 | 0.0049 | 2026-04-15 |
CVE-2026-60074 UPD | 5.9 | 7.5 | 0.0063 | 2026-07-30 |
CVE-2024-42219 | 5.8 | 7.8 | 0.0031 | 2024-08-06 |
CVE-2026-49942 UPD | 5.7 | 7.3 | 0.0049 | 2026-06-04 |
CVE-2026-101015 | 5.6 | 7.3 | 0.0029 | 2026-09-28 |
CVE-2026-33515 | 5.4 | 6.5 | 0.0104 | 2026-03-26 |
CVE-2026-47729 | 5.4 | 6.5 | 0.0150 | 2026-07-16 |
CVE-2026-41239 | 5.2 | 6.8 | 0.0041 | 2026-04-23 |
CVE-2026-45190 UPD | 5.2 | 6.5 | 0.0048 | 2026-05-10 |
CVE-2026-45191 UPD | 5.2 | 6.5 | 0.0048 | 2026-05-10 |
CVE-2026-42462 | 5.2 | 7.0 | 0.0025 | 2026-06-10 |