CWE · MITRE source
CWE-356Product UI does not Warn User of Unsafe Actions
The product's user interface does not warn the user before undertaking an unsafe action on behalf of that user. This makes it easier for attackers to trick users into inflicting damage to their system.
Product systems should warn users that a potentially dangerous action may occur if the user proceeds. For example, if the user downloads a file from an unknown source and attempts to execute the file on their machine, then the application's GUI can indicate that the file is unsafe.
Last updated: 04 July 2026 08:17 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 · 5 mapping(s) from 2 framework(s): ATT&CK 4 (mostly) · OWASP-Web 1 (full)
NIST 800-53 r5 controls that address this weakness (1)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-15 | Collaborative Computing Devices and Applications | SC | Mandates explicit user-visible indication, directly countering absence of warnings for device activation. |
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-2018-16858 | 8.0 | 7.8 | 0.6755 | 2019-03-25 |
CVE-2019-6736 | 5.5 | 8.8 | 0.0367 | 2019-06-03 |
CVE-2019-6737 | 5.5 | 8.8 | 0.0382 | 2019-06-03 |
CVE-2019-6738 | 5.5 | 8.8 | 0.0367 | 2019-06-03 |
CVE-2019-13322 | 5.5 | 8.8 | 0.0255 | 2020-02-10 |
CVE-2022-35873 | 5.5 | 7.8 | 0.0066 | 2022-07-25 |
CVE-2022-39362 | 5.5 | 8.8 | 0.0079 | 2022-10-26 |
CVE-2022-36970 | 5.5 | 7.8 | 0.0065 | 2023-03-29 |
CVE-2025-2450 | 5.5 | 8.8 | 0.0048 | 2025-03-18 |
CVE-2025-3909 UPD | 5.5 | 8.1 | 0.0036 | 2025-05-14 |
CVE-2025-14402 | 5.5 | 7.0 | 0.0022 | 2025-12-23 |
CVE-2025-14403 | 5.5 | 7.8 | 0.0026 | 2025-12-23 |
CVE-2025-14404 | 5.5 | 7.0 | 0.0022 | 2025-12-23 |
CVE-2025-14412 | 5.5 | 7.8 | 0.0016 | 2025-12-23 |
CVE-2025-14414 | 5.5 | 7.8 | 0.0018 | 2025-12-23 |
CVE-2025-14415 | 5.5 | 7.8 | 0.0021 | 2025-12-23 |
CVE-2025-14416 | 5.5 | 7.0 | 0.0014 | 2025-12-23 |
CVE-2025-14417 | 5.5 | 7.8 | 0.0016 | 2025-12-23 |
CVE-2025-14418 | 5.5 | 7.0 | 0.0014 | 2025-12-23 |
CVE-2025-3839 | 5.5 | 8.0 | 0.0038 | 2026-01-23 |
CVE-2026-0777 | 5.5 | 7.8 | 0.0034 | 2026-02-20 |
CVE-2018-10593 | 3.5 | 5.6 | 0.0037 | 2018-05-24 |
CVE-2018-10595 | 3.5 | 6.3 | 0.0041 | 2018-05-24 |
CVE-2019-17151 | 3.5 | 5.4 | 0.0137 | 2020-01-07 |
CVE-2024-2609 UPD | 3.5 | 6.1 | 0.0060 | 2024-03-19 |