Base weakness

Draft

CWE-447: Unimplemented or Unsupported Feature in UI

A UI function for a security feature appears to be supported and gives feedback to the user that suggests that it is supported, but the underlying functionality is not implemented.

Last updated May 1, 2026

3

Recorded CVEs

With this primary weakness

0

KEVs

In the CISA KEV catalog

Not rated

Likelihood of exploit

Per MITRE

Base

Abstraction

MITRE classification

Overview

CWE-447 (Unimplemented or Unsupported Feature in UI) is a base-level software weakness catalogued by MITRE in the Common Weakness Enumeration (CWE). It describes a recurring type of mistake that can lead to exploitable security vulnerabilities.

Real-world CVEs

3 recorded CVEs are caused by CWE-447 (Unimplemented or Unsupported Feature in UI). The highest-severity and most recent are shown first. 0 new CWE-447 CVEs have been recorded so far in 2026 (1 in 2025).

Common consequences

What can happen when CWE-447 is exploited.

Varies by Context, Unexpected State

Affects: Other

How it happens

When it is introduced

Typically introduced during these phases of the software lifecycle.

Implementation

How to prevent it

Practical mitigations for CWE-447, grouped by where in the lifecycle they apply.

Testing

Perform functionality testing before deploying the application.

Illustrative examples

Real CVEs that MITRE cites as examples of this weakness.

CVE-2000-0127 — GUI configuration tool does not enable a security option when a checkbox is selected, although that option is honored when manually set in the configuration file.
CVE-2001-0863 — Router does not implement a specific keyword when it is used in an ACL, allowing filter bypass.
CVE-2001-0865 — Router does not implement a specific keyword when it is used in an ACL, allowing filter bypass.
CVE-2004-0979 — Web browser does not properly modify security setting when the user sets it.

Terminology & mappings

Mapped taxonomies

PLOVER: Unimplemented or unsupported feature in UI

Frequently asked questions

Common questions about CWE-447.

What is CWE-447?

A UI function for a security feature appears to be supported and gives feedback to the user that suggests that it is supported, but the underlying functionality is not implemented.

What CVEs are caused by CWE-447?

3 recorded CVEs are attributed to CWE-447, including CVE-2024-0148, CVE-2024-39533, CVE-2024-21607.

How do you prevent CWE-447?

Perform functionality testing before deploying the application.

What are the consequences of CWE-447?

Exploiting CWE-447 can lead to: Varies by Context, Unexpected State.

Is CWE-447 actively exploited?

3 recorded CVEs are caused by CWE-447; none are currently in CISA's KEV catalog of actively exploited flaws.

References

Weakness data is sourced from the MITRE CWE catalog (v4.20). CVE associations are aggregated and kept current by RadicalNotion.AI.

Stay ahead of CWE-447

Get alerted the moment a new CWE-447 vulnerability affects your stack, with AI-written analysis, severity context, and remediation guidance.

Start free See pricing