CWE · MITRE source
CWE-1286Improper Validation of Syntactic Correctness of Input
The product receives input that is expected to be well-formed - i.e., to comply with a certain syntax - but it does not validate or incorrectly validates that the input complies with the syntax.
Often, complex inputs are expected to follow a particular syntax, which is either assumed by the input itself, or declared within metadata such as headers. The syntax could be for data exchange formats, markup languages, or even programming languages. When untrusted input is not properly validated for the expected syntax, attackers could cause parsing failures, trigger unexpected errors, or expose latent vulnerabilities that might not be directly exploitable if the input had conformed to the syntax.
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 · 8 mapping(s) from 3 framework(s): ASVS 5.0 5 (mostly) · CAPEC 2 (partial) · 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-2024-7954 | 8.0 | 9.8 | 0.8978 | 2024-08-23 |
CVE-2021-28812 | 5.5 | 8.8 | 0.0155 | 2021-06-03 |
CVE-2021-31987 | 5.5 | 7.5 | 0.0086 | 2021-10-05 |
CVE-2021-31988 | 5.5 | 8.8 | 0.0092 | 2021-10-05 |
CVE-2022-22176 | 5.5 | 7.4 | 0.0037 | 2022-01-19 |
CVE-2022-1941 | 5.5 | 7.5 | 0.0119 | 2022-09-22 |
CVE-2022-22192 | 5.5 | 7.5 | 0.0070 | 2022-10-18 |
CVE-2023-28985 | 5.5 | 7.5 | 0.0052 | 2023-07-14 |
CVE-2023-32649 | 5.5 | 7.5 | 0.0053 | 2023-09-19 |
CVE-2024-21595 UPD | 5.5 | 7.5 | 0.0054 | 2024-01-12 |
CVE-2024-21616 UPD | 5.5 | 7.5 | 0.0053 | 2024-01-12 |
CVE-2024-0218 | 5.5 | 7.5 | 0.0055 | 2024-04-10 |
CVE-2024-3384 | 5.5 | 7.5 | 0.0089 | 2024-04-10 |
CVE-2024-21598 | 5.5 | 7.5 | 0.0057 | 2024-04-12 |
CVE-2024-26507 | 5.5 | 7.8 | 0.0019 | 2024-06-10 |
CVE-2024-6284 | 5.5 | 7.3 | 0.0029 | 2024-07-03 |
CVE-2024-39542 | 5.5 | 7.5 | 0.0047 | 2024-07-11 |
CVE-2025-0638 | 5.5 | 7.5 | 0.0046 | 2025-01-22 |
CVE-2025-22868 | 5.5 | 7.5 | 0.0080 | 2025-02-26 |
CVE-2025-24346 UPD | 5.5 | 7.5 | 0.0040 | 2025-04-30 |
CVE-2025-30415 UPD | 5.5 | 7.5 | 0.0032 | 2025-06-04 |
CVE-2024-51982 UPD | 5.5 | 7.5 | 0.0679 | 2025-06-25 |
CVE-2024-51983 UPD | 5.5 | 7.5 | 0.0747 | 2025-06-25 |
CVE-2025-11573 | 5.5 | 7.5 | 0.0039 | 2025-10-09 |
CVE-2025-55085 | 5.5 | 7.5 | 0.0055 | 2025-10-17 |