This vulnerability occurs when a user interface (UI) includes outdated or deprecated features, but fails to alert users about their obsolete status. This can mislead users into relying on functionality that may be broken, unsupported, or pose a security risk.
Obsolete UI features are problematic because they create a mismatch between user expectations and system reality. Users might depend on these features for critical tasks, unaware that the underlying code may be unstable, removed from backend services, or no longer receiving security updates. This reliance can lead to unexpected errors, data loss, or expose attack surfaces that developers are no longer monitoring. To prevent this, development teams should implement a clear feature lifecycle within the UI. Actively deprecate old elements by adding visual warnings (like strikethrough text, 'Deprecated' badges, or tooltips) that inform users and guide them toward modern alternatives. Regularly audit the UI against backend API changes and establish a process for removing legacy features entirely after a communicated sunset period.
Impact: Quality DegradationVaries by Context