Product UI does not Warn User of Unsafe Actions

Incomplete Base
Structure: Simple
Description

This vulnerability occurs when a software interface fails to alert users before they perform a risky action. Without clear warnings, users can be more easily misled into taking steps that harm their system or data.

Extended Description

A secure user interface acts as a safety checkpoint, clearly informing users when an action could be dangerous—like installing software from an untrusted source or permanently deleting critical data. These warnings should be prominent, use plain language, and require explicit user confirmation to proceed, helping prevent accidental or socially-engineered mistakes. For developers, this means building proactive confirmation dialogs or banners for high-risk operations such as file execution, financial transactions, or system changes. The warning should explain the specific risk (e.g., 'This file came from outside your organization') and offer a safe alternative, empowering users to make informed security decisions rather than blindly proceeding.

Common Consequences 1
Scope: Non-Repudiation

Impact: Hide Activities

Observed Examples 6
CVE-1999-1055Product does not warn user when document contains certain dangerous functions or macros.
CVE-1999-0794Product does not warn user when document contains certain dangerous functions or macros.
CVE-2000-0277Product does not warn user when document contains certain dangerous functions or macros.
CVE-2000-0517Product does not warn user about a certificate if it has already been accepted for a different site. Possibly resultant.
CVE-2005-0602File extractor does not warn user if setuid/setgid files could be extracted. Overlaps privileges/permissions.
CVE-2000-0342E-mail client allows bypass of warning for dangerous attachments via a Windows .LNK file that refers to the attachment.
Applicable Platforms
Languages:
Not Language-Specific : Undetermined
Modes of Introduction
Architecture and Design
Implementation
Related Weaknesses
Taxonomy Mapping
  • PLOVER
Notes
RelationshipOften resultant, e.g. in unhandled error conditions.
RelationshipCan overlap privilege errors, conceptually at least.