CWE · MITRE source
CWE-183Permissive List of Allowed Inputs
The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are explicitly allowed by policy because the inputs are assumed to be safe, but the list is too permissive - that is, it allows an input that is unsafe, leading to resultant weaknesses.
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 · 7 mapping(s) from 4 framework(s): CAPEC 4 (partial) · ASVS 5.0 1 (mostly) · OWASP-Web 1 (mostly) · ATT&CK 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A06:2025 Insecure Design.
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-3490 | 7.0 | 10.0 | 0.0062 | 2026-06-17 |
CVE-2026-54316 | 7.0 | 9.1 | 0.0040 | 2026-06-23 |
CVE-2020-25696 | 5.5 | 7.5 | 0.0259 | 2020-11-23 |
CVE-2024-1654 UPD | 5.5 | 7.2 | 0.0131 | 2024-03-14 |
CVE-2025-24349 UPD | 5.5 | 7.1 | 0.0048 | 2025-04-30 |
CVE-2025-53762 UPD | 5.5 | 8.7 | 0.0074 | 2025-07-18 |
CVE-2025-59457 | 5.5 | 7.7 | 0.0075 | 2025-09-17 |
CVE-2026-33979 | 5.5 | 8.2 | 0.0038 | 2026-03-27 |
CVE-2026-42043 UPD | 5.5 | 7.2 | 0.0066 | 2026-04-24 |
CVE-2026-41387 | 5.5 | 7.8 | 0.0024 | 2026-04-28 |
CVE-2026-29514 UPD | 5.5 | 8.8 | 0.0078 | 2026-05-04 |
CVE-2026-50189 | 5.5 | 7.2 | 0.0027 | 2026-06-24 |
CVE-2026-46608 | 5.5 | 7.4 | 0.0040 | 2026-06-25 |
CVE-2020-1694 | 3.5 | 4.9 | 0.0164 | 2020-09-16 |
CVE-2021-34787 | 3.5 | 5.3 | 0.0100 | 2021-10-27 |
CVE-2021-40128 | 3.5 | 5.3 | 0.0095 | 2021-11-04 |
CVE-2022-23158 | 3.5 | 6.0 | 0.0069 | 2022-04-01 |
CVE-2022-34450 | 3.5 | 6.7 | 0.0042 | 2023-02-11 |
CVE-2022-42469 | 3.5 | 4.3 | 0.0044 | 2023-04-11 |
CVE-2023-4399 | 3.5 | 6.6 | 0.0108 | 2023-10-17 |
CVE-2023-7250 | 3.5 | 5.3 | 0.0093 | 2024-03-18 |
CVE-2024-38522 | 3.5 | 6.3 | 0.0035 | 2024-06-28 |
CVE-2024-47565 | 3.5 | 4.3 | 0.0037 | 2024-10-08 |
CVE-2026-2302 | 3.5 | 6.5 | 0.0020 | 2026-02-10 |
CVE-2026-2303 | 3.5 | 6.5 | 0.0022 | 2026-02-10 |