CWE-183: Permissive List of Allowed Inputs
low-riskThe 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.
Common Consequences
Detection Methods
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Real-World Examples (10)
| CVE | CVSS | EPSS | KEV |
|---|---|---|---|
| CVE-2024-1654 | 7.2 | 4.2% | — |
| CVE-2021-34787 | 5.3 | 1.2% | — |
| CVE-2025-53762 | 8.7 | 0.6% | — |
| CVE-2020-25696 | 7.5 | 0.5% | — |
| CVE-2025-24349 | 7.1 | 0.3% | — |
| CVE-2020-1694 | 4.9 | 0.3% | — |
| CVE-2026-32881 | 5.3 | 0.2% | — |
| CVE-2024-47565 | 4.3 | 0.1% | — |
| CVE-2022-34450 | 6.7 | 0.1% | — |
| CVE-2021-40128 | 5.3 | 0.1% | — |