CWE · MITRE source
CWE-1288Improper Validation of Consistency within Input
The product receives a complex input with multiple elements or fields that must be consistent with each other, but it does not validate or incorrectly validates that the input is actually consistent.
Some input data can be structured with multiple elements or fields that must be consistent with each other, e.g. a number-of-items field that is followed by the expected number of elements. When such complex inputs are inconsistent, attackers could trigger unexpected errors, cause incorrect actions to take place, or exploit latent vulnerabilities.
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 · 4 mapping(s) from 2 framework(s): ASVS 5.0 2 (mostly) · ATT&CK 2 (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-31431 KEV UPD | 10.0 | 7.8 | 0.9627 | 2026-04-22 |
CVE-2022-39353 | 7.0 | 9.4 | 0.0118 | 2022-11-02 |
CVE-2021-41531 | 5.5 | 7.5 | 0.0090 | 2021-09-21 |
CVE-2023-32701 | 5.5 | 7.1 | 0.0024 | 2023-11-14 |
CVE-2023-6245 | 5.5 | 7.5 | 0.0121 | 2023-12-08 |
CVE-2024-25951 UPD | 5.5 | 8.0 | 0.0083 | 2024-03-09 |
CVE-2024-31136 UPD | 5.5 | 7.4 | 0.0054 | 2024-03-28 |
CVE-2024-39515 | 5.5 | 7.5 | 0.0044 | 2024-10-09 |
CVE-2022-50976 | 5.5 | 7.7 | 0.0014 | 2026-02-02 |
CVE-2026-31488 UPD | 5.5 | 7.8 | 0.0014 | 2026-04-22 |
CVE-2026-43001 UPD | 5.5 | 7.9 | 0.0045 | 2026-05-01 |
CVE-2026-31709 UPD | 5.5 | 8.8 | 0.0026 | 2026-05-01 |
CVE-2026-46117 UPD | 5.5 | 7.8 | 0.0013 | 2026-05-28 |
CVE-2023-1619 | 3.5 | 4.9 | 0.0079 | 2023-06-26 |
CVE-2023-1620 | 3.5 | 4.9 | 0.0085 | 2023-06-26 |
CVE-2024-31140 UPD | 3.5 | 4.1 | 0.0043 | 2024-03-28 |
CVE-2024-27371 | 3.5 | 6.7 | 0.0020 | 2024-06-05 |
CVE-2024-27375 | 3.5 | 6.7 | 0.0020 | 2024-06-05 |
CVE-2024-5953 | 3.5 | 5.7 | 0.0057 | 2024-06-18 |
CVE-2024-8305 | 3.5 | 6.5 | 0.0057 | 2024-10-21 |
CVE-2025-2885 | 3.5 | 4.5 | 0.0031 | 2025-03-27 |
CVE-2024-12093 | 3.5 | 6.8 | 0.0041 | 2025-05-22 |
CVE-2025-46722 UPD | 3.5 | 4.2 | 0.0027 | 2025-05-29 |
CVE-2025-10929 | 3.5 | 5.3 | 0.0028 | 2025-10-30 |
CVE-2026-9689 UPD | 3.5 | 4.2 | 0.0021 | 2026-05-27 |