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.
View on MITREProduct 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.
No mitigation information available for this CWE.
No detection method information available for this CWE.
Product does not warn user when document contains certain dangerous functions or macros.
View DetailsProduct does not warn user when document contains certain dangerous functions or macros.
View DetailsProduct does not warn user when document contains certain dangerous functions or macros.
View DetailsProduct does not warn user about a certificate if it has already been accepted for a different site. Possibly resultant.
View DetailsFile extractor does not warn user if setuid/setgid files could be extracted. Overlaps privileges/permissions.
View DetailsE-mail client allows bypass of warning for dangerous attachments via a Windows .LNK file that refers to the attachment.
View DetailsCWE-356: Product UI does not Warn User of Unsafe Actions is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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.
If exploited, CWE-356 (Product UI does not Warn User of Unsafe Actions) it can compromise Non-Repudiation, leading to outcomes such as Hide Activities.
CWE-356 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.
MITRE documents real CVEs mapped to CWE-356, including CVE-1999-1055, CVE-1999-0794, CVE-2000-0277, CVE-2000-0517 and CVE-2005-0602. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.
A CWE (Common Weakness Enumeration) like CWE-356 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.