CWE Reference

CWE-448: Obsolete Feature in UI

Official CWE-448 CWE context with Glexia analysis, remediation guidance, related CVEs, and ATT&CK context.

Release 4.20weaknessDraft

Glexia's Take

CWE-448: Obsolete Feature in UI

Obsolete Feature in UI represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Executive Impact

Other: Quality Degradation,Varies by Context

Developer Pattern

CWE-448 is the kind of defect developers can usually prevent with explicit validation, safer framework defaults, and tests that exercise hostile input or unsafe state transitions.

Confidence

high confidence from CWE-448, 4.20.

Official CWE Definition

CWE-448: Obsolete Feature in UI

A UI function is obsolete and the product does not warn the user.

Type: weakness
Abstraction: Base
Status: Draft
Source: MITRE CWE definition

Developer And Remediation Guidance

How teams prevent and detect this weakness

Causes

Missing validation
Unsafe defaults
Insufficient authorization or memory-safety invariant

Remediation

Architecture and Design: Remove the obsolete feature from the UI. Warn the user that the feature is no longer supported.

Detection

Code review
SAST
DAST
Focused regression tests

Mappings

Related CVEs, CWEs, and ATT&CK context

Related CWEs

CWE-446: UI Discrepancy for Security Feature

Related CVEs

Related CVE mappings appear after CVE records are cross-indexed.

Open CWE CVE mapping

ATT&CK Relevance

ATT&CK relevance is shown only when reviewed or responsibly inferred.