CWE · MITRE source
CWE-1173Improper Use of Validation Framework
The product does not use, or incorrectly uses, an input validation framework that is provided by the source language or an independent library.
Many modern coding languages provide developers with input validation frameworks to make the task of input validation easier and less error-prone. These frameworks will automatically check all input against specified criteria and direct execution to error handlers when invalid input is received. The improper use (i.e., an incorrect implementation or missing altogether) of these frameworks is not directly exploitable, but can lead to an exploitable condition if proper input validation is not performed later in the product. Not using provided input validation frameworks can also hurt the maintainability of code as future developers may not recognize the downstream input validation being used in the place of the validation framework.
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: mostly · 12 mapping(s) from 4 framework(s): ATT&CK 5 (partial) · ISO_IEC_27002_2022 3 (mostly) · 800-53 3 (mostly) · 1 (mostly)
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
—
—
V2.2.2V1.3.1V1.4.2V15.3.7
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-33454 UPD | 7.3 | 9.4 | 0.0149 | 2026-04-27 |
CVE-2022-1414 UPD | 6.7 | 8.8 | 0.0094 | 2022-10-19 |
CVE-2020-1640 UPD | 6.1 | 7.5 | 0.0139 | 2020-07-17 |
CVE-2023-29091 UPD | 5.2 | 6.8 | 0.0080 | 2023-04-14 |
CVE-2024-58360 UPD | 5.2 | 6.5 | 0.0045 | 2026-07-16 |
CVE-2025-3940 UPD | 4.4 | 5.3 | 0.0037 | 2025-05-22 |
CVE-2023-30949 UPD | 3.5 | 4.3 | 0.0020 | 2023-07-26 |
CVE-2026-33674 | 2.0 | 2.0 | 0.0025 | 2026-03-26 |