CWE · MITRE source
CWE-707Improper Neutralization
The product does not ensure or incorrectly ensures that structured messages or data are well-formed and that certain security properties are met before being read from an upstream component or sent to a downstream component.
If a message is malformed, it may cause the message to be incorrectly interpreted. Neutralization is an abstract term for any technique that ensures that input (and output) conforms with expectations and is "safe." This can be done by: This weakness typically applies in cases where the product prepares a control message that another process must act on, such as a command or query, and malicious input that was intended as data, can enter the control plane instead. However, this weakness also applies to more general cases where there are not always control implications.
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 · 21 mapping(s) from 4 framework(s): CAPEC 16 (partial) · ATT&CK 3 (partial) · ASVS 5.0 1 (mostly) · STIG oracle linux 9 1 (partial)
NIST 800-53 r5 controls that address this weakness (1)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SA-15 | Development Process, Standards, and Tools | SA | Enforces use of documented standards and tool configurations that address proper neutralization of inputs/outputs during development. |
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-43572 KEV | 10.0 | 7.8 | 0.6095 | 2024-10-08 |
CVE-2025-26633 KEV | 10.0 | 7.0 | 0.3189 | 2025-03-11 |
CVE-2024-10914 | 8.0 | 8.1 | 0.9743 | 2024-11-06 |
CVE-2024-10915 | 8.0 | 8.1 | 0.7913 | 2024-11-06 |
CVE-2022-3801 | 6.0 | 6.3 | 0.3008 | 2022-11-01 |
CVE-2022-4257 | 6.0 | 6.3 | 0.4393 | 2022-12-01 |
CVE-2018-3918 | 5.5 | 7.5 | 0.0099 | 2018-08-27 |
CVE-2019-10052 | 5.5 | 7.5 | 0.0212 | 2019-08-28 |
CVE-2020-11026 | 5.5 | 8.7 | 0.0209 | 2020-04-30 |
CVE-2022-3495 | 5.5 | 7.3 | 0.0063 | 2022-10-14 |
CVE-2022-3583 | 5.5 | 7.3 | 0.0066 | 2022-10-18 |
CVE-2022-3878 | 5.5 | 7.3 | 0.0065 | 2022-11-07 |
CVE-2022-3955 | 5.5 | 7.3 | 0.0066 | 2022-11-11 |
CVE-2022-3972 | 5.5 | 7.3 | 0.0056 | 2022-11-13 |
CVE-2022-3973 | 5.5 | 7.3 | 0.0056 | 2022-11-13 |
CVE-2022-4088 | 5.5 | 7.3 | 0.0056 | 2022-11-24 |
CVE-2023-6123 | 5.5 | 7.5 | 0.0051 | 2024-02-15 |
CVE-2023-42773 | 5.5 | 8.8 | 0.0022 | 2024-05-16 |
CVE-2023-46689 | 5.5 | 8.8 | 0.0022 | 2024-05-16 |
CVE-2024-21864 | 5.5 | 7.8 | 0.0034 | 2024-05-16 |
CVE-2024-10752 | 5.5 | 7.3 | 0.0060 | 2024-11-04 |
CVE-2024-10791 | 5.5 | 7.3 | 0.0059 | 2024-11-04 |
CVE-2024-10844 | 5.5 | 7.3 | 0.0089 | 2024-11-05 |
CVE-2024-10845 | 5.5 | 7.3 | 0.0089 | 2024-11-05 |
CVE-2026-5002 | 5.5 | 7.3 | 0.0030 | 2026-03-28 |