CWE · MITRE source
CWE-358Improperly Implemented Security Check for Standard
The product does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique.
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: full · 3 mapping(s) from 2 framework(s): ATT&CK 2 (full) · ASVS 5.0 1 (full)
NIST 800-53 r5 controls that address this weakness (1)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
CA-2 | Control Assessments | CA | Assessments identify and document improperly implemented security checks, allowing fixes that reduce exploitation of flawed checks. |
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-7965 KEV | 10.0 | 8.8 | 0.1723 | 2024-08-21 |
CVE-2018-1270 | 8.0 | 9.8 | 0.7724 | 2018-04-06 |
CVE-2018-1275 | 8.0 | 9.8 | 0.5763 | 2018-04-11 |
CVE-2016-10229 | 7.0 | 9.8 | 0.1279 | 2017-04-04 |
CVE-2018-0268 | 7.0 | 10.0 | 0.0540 | 2018-05-17 |
CVE-2019-6742 | 7.0 | 9.8 | 0.0592 | 2019-06-03 |
CVE-2022-25152 | 7.0 | 9.9 | 0.0166 | 2022-06-09 |
CVE-2023-39403 | 7.0 | 9.1 | 0.0032 | 2023-08-13 |
CVE-2023-3266 | 7.0 | 9.8 | 0.0082 | 2023-08-14 |
CVE-2023-4501 | 7.0 | 9.8 | 0.0062 | 2023-09-12 |
CVE-2025-62583 | 7.0 | 9.8 | 0.0046 | 2025-10-16 |
CVE-2025-69234 | 7.0 | 9.1 | 0.0025 | 2025-12-30 |
CVE-2025-66603 | 7.0 | 9.8 | 0.0026 | 2026-02-09 |
CVE-2026-29103 | 7.0 | 9.1 | 0.0050 | 2026-03-19 |
CVE-2026-50628 UPD | 7.0 | 9.8 | 0.0063 | 2026-06-12 |
CVE-2017-15663 | 6.0 | 7.5 | 0.1318 | 2018-01-10 |
CVE-2024-2174 UPD | 6.0 | 8.8 | 0.1256 | 2024-03-06 |
CVE-2016-3017 | 5.5 | 7.5 | 0.0222 | 2017-02-01 |
CVE-2017-7177 | 5.5 | 7.5 | 0.0126 | 2017-03-18 |
CVE-2017-15662 | 5.5 | 7.5 | 0.0915 | 2018-01-10 |
CVE-2017-15664 | 5.5 | 7.5 | 0.0915 | 2018-01-10 |
CVE-2017-15665 | 5.5 | 7.5 | 0.0915 | 2018-01-10 |
CVE-2017-15091 | 5.5 | 7.1 | 0.0126 | 2018-01-23 |
CVE-2017-15107 | 5.5 | 7.5 | 0.0270 | 2018-01-23 |
CVE-2018-1243 | 5.5 | 7.5 | 0.0182 | 2018-07-02 |