CWE · MITRE source
CWE-1287Improper Validation of Specified Type of Input
The product receives input that is expected to be of a certain type, but it does not validate or incorrectly validates that the input is actually of the expected type.
When input does not comply with the expected type, attackers could trigger unexpected errors, cause incorrect actions to take place, or exploit latent vulnerabilities that would not be possible if the input conformed with the expected type. This weakness can appear in type-unsafe programming languages, or in programming languages that support casting or conversion of an input to another type.
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 · 9 mapping(s) from 2 framework(s): ASVS 5.0 5 (full) · ATT&CK 4 (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-2024-4879 KEV | 10.0 | 9.8 | 0.9998 | 2024-07-10 |
CVE-2021-43802 | 7.0 | 9.9 | 0.0199 | 2021-12-09 |
CVE-2021-32024 | 7.0 | 9.8 | 0.0179 | 2021-12-13 |
CVE-2024-35213 | 7.0 | 9.0 | 0.0052 | 2024-06-11 |
CVE-2024-6298 | 7.0 | 10.0 | 0.1901 | 2024-07-05 |
CVE-2024-51550 | 7.0 | 10.0 | 0.0182 | 2024-12-05 |
CVE-2024-51551 | 7.0 | 10.0 | 0.0045 | 2024-12-05 |
CVE-2024-5594 | 7.0 | 9.1 | 0.0080 | 2025-01-06 |
CVE-2025-12977 | 7.0 | 9.1 | 0.0063 | 2025-11-24 |
CVE-2026-24307 | 7.0 | 9.3 | 0.0081 | 2026-01-22 |
CVE-2026-44935 | 7.0 | 9.9 | 0.0057 | 2026-07-02 |
CVE-2022-31007 | 6.0 | 4.9 | 0.2610 | 2022-05-31 |
CVE-2022-20783 | 5.5 | 7.5 | 0.0133 | 2022-04-21 |
CVE-2022-22228 | 5.5 | 7.5 | 0.0062 | 2022-10-18 |
CVE-2022-39369 | 5.5 | 8.0 | 0.0106 | 2022-11-01 |
CVE-2022-43723 | 5.5 | 7.5 | 0.0092 | 2022-12-13 |
CVE-2023-28799 | 5.5 | 8.2 | 0.0044 | 2023-06-22 |
CVE-2024-30395 | 5.5 | 7.5 | 0.0054 | 2024-04-12 |
CVE-2023-47726 | 5.5 | 7.1 | 0.0037 | 2024-06-18 |
CVE-2024-47504 | 5.5 | 7.5 | 0.0059 | 2024-10-11 |
CVE-2024-20408 | 5.5 | 7.7 | 0.0045 | 2024-10-23 |
CVE-2024-20494 | 5.5 | 8.6 | 0.0052 | 2024-10-23 |
CVE-2024-43426 | 5.5 | 7.5 | 0.0060 | 2024-11-07 |
CVE-2024-8403 | 5.5 | 7.5 | 0.0066 | 2024-11-19 |
CVE-2024-9404 | 5.5 | 7.5 | 0.0076 | 2024-12-04 |