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: 06 November 2026 08:24 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: full · 59 mapping(s) from 5 framework(s): ATT&CK 52 (full) · ISO_IEC_27002_2022 4 (mostly) · ASVS 5.0 1 (mostly) · 1 (mostly) · 800-53 1 (mostly)
OWASP Top 10 for Web (2025)
This weakness contributes to A06:2025 Insecure Design.
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
—
—
V1.5.2V4.4.2
NIST 800-53 r5 controls PROPOSED for this weakness (0)
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| 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).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2026-3490 UPD | 7.5 | 10.0 | 0.0082 | 2026-06-17 |
CVE-2026-54316 UPD | 6.9 | 9.1 | 0.0052 | 2026-06-23 |
CVE-2026-54694 | 6.8 | 9.6 | 0.0047 | 2026-09-09 |
CVE-2026-29514 UPD | 6.7 | 8.8 | 0.0078 | 2026-05-04 |
CVE-2025-53762 UPD | 6.4 | 8.7 | 0.0091 | 2025-07-18 |
CVE-2026-55581 UPD | 6.3 | 8.4 | 0.0045 | 2026-08-25 |
CVE-2020-25696 UPD | 6.2 | 7.5 | 0.0270 | 2020-11-23 |
CVE-2026-33979 | 6.2 | 8.2 | 0.0039 | 2026-03-27 |
CVE-2026-67345 UPD | 6.2 | 8.1 | 0.0056 | 2026-07-30 |
CVE-2026-115915 | 6.2 | 8.1 | 0.0066 | 2026-10-26 |
CVE-2025-59457 | 5.8 | 7.7 | 0.0083 | 2025-09-17 |
CVE-2026-59802 UPD | 5.8 | 8.2 | 0.0024 | 2026-07-08 |
CVE-2026-67315 UPD | 5.8 | 7.5 | 0.0046 | 2026-08-01 |
CVE-2024-1654 UPD | 5.7 | 7.2 | 0.0131 | 2024-03-14 |
CVE-2026-41387 | 5.7 | 7.8 | 0.0024 | 2026-04-28 |
CVE-2026-103687 | 5.7 | 7.3 | 0.0042 | 2026-10-01 |
CVE-2026-116339 | 5.7 | 7.3 | 0.0048 | 2026-10-26 |
CVE-2025-24349 UPD | 5.6 | 7.1 | 0.0066 | 2025-04-30 |
CVE-2026-106510 | 5.6 | 7.7 | 0.0048 | 2026-10-07 |
CVE-2026-21915 UPD | 5.5 | 6.7 | 0.0224 | 2026-04-09 |
CVE-2026-42043 UPD | 5.5 | 7.2 | 0.0071 | 2026-04-24 |
CVE-2026-50189 UPD | 5.5 | 7.2 | 0.0049 | 2026-06-24 |
CVE-2026-46608 UPD | 5.4 | 7.4 | 0.0040 | 2026-06-25 |
CVE-2026-96229 UPD | 5.3 | 6.5 | 0.0095 | 2026-10-13 |
CVE-2022-34450 UPD | 5.1 | 6.7 | 0.0042 | 2023-02-11 |