CWE · MITRE source
CWE-184Incomplete List of Disallowed Inputs
The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete.
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 · 10 mapping(s) from 3 framework(s): CAPEC 8 (partial) · ASVS 5.0 1 (mostly) · ATT&CK 1 (partial)
NIST 800-53 r5 controls that address this weakness (1)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SI-8 | Spam Protection | SI | Spam filters rely on evolving blacklists, signatures, and heuristics of disallowed message patterns; keeping them updated per the control directly mitigates incomplete disallowed-input lists. |
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-5217 KEV | 10.0 | 9.8 | 0.9963 | 2024-07-10 |
CVE-2022-43396 | 8.0 | 8.8 | 0.5684 | 2022-12-30 |
CVE-2017-7540 | 7.0 | 9.8 | 0.0163 | 2017-07-21 |
CVE-2017-0909 | 7.0 | 9.8 | 0.0203 | 2017-11-16 |
CVE-2017-15095 | 7.0 | 9.8 | 0.0841 | 2018-02-06 |
CVE-2017-7525 | 7.0 | 9.8 | 0.3792 | 2018-02-06 |
CVE-2018-7489 | 7.0 | 9.8 | 0.2052 | 2018-02-26 |
CVE-2019-9212 | 7.0 | 9.8 | 0.0276 | 2019-02-27 |
CVE-2023-3374 | 7.0 | 9.8 | 0.0058 | 2023-09-05 |
CVE-2023-45133 | 7.0 | 9.3 | 0.0052 | 2023-10-12 |
CVE-2024-51745 | 7.0 | 10.0 | 0.0081 | 2024-11-05 |
CVE-2025-1716 | 7.0 | 9.8 | 0.0159 | 2025-02-26 |
CVE-2025-58361 UPD | 7.0 | 9.3 | 0.0026 | 2025-09-04 |
CVE-2026-28363 | 7.0 | 9.9 | 0.0050 | 2026-02-27 |
CVE-2026-28783 | 7.0 | 9.1 | 0.0046 | 2026-03-04 |
CVE-2026-32940 | 7.0 | 9.3 | 0.0030 | 2026-03-20 |
CVE-2026-33396 | 7.0 | 9.9 | 0.0083 | 2026-03-26 |
CVE-2026-34177 | 7.0 | 9.1 | 0.0036 | 2026-04-09 |
CVE-2026-34415 | 7.0 | 9.8 | 0.0357 | 2026-04-22 |
CVE-2026-41264 | 7.0 | 9.8 | 0.0103 | 2026-04-23 |
CVE-2026-43566 UPD | 7.0 | 9.1 | 0.0042 | 2026-05-05 |
CVE-2026-43578 UPD | 7.0 | 9.1 | 0.0029 | 2026-05-06 |
CVE-2026-55743 | 7.0 | 9.6 | 0.0070 | 2026-06-17 |
CVE-2025-71320 | 7.0 | 9.8 | 0.0062 | 2026-06-17 |
CVE-2025-71323 | 7.0 | 9.8 | 0.0076 | 2026-06-17 |