What CVEs are caused by CWE-623?

3 recorded CVEs are attributed to CWE-623, including CVE-2011-10028, CVE-2014-2368, CVE-2018-17925.

What are the consequences of CWE-623?

Exploiting CWE-623 can lead to: Execute Unauthorized Code or Commands.

Is CWE-623 actively exploited?

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

RadicalNotion.AI

Log in Start free

Log in

Log in Start free

Variant weakness

Draft

CWE-623: Unsafe ActiveX Control Marked Safe For Scripting

An ActiveX control is intended for restricted use, but it has been marked as safe-for-scripting.

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

Variant

Abstraction

MITRE classification

Overview

This might allow attackers to use dangerous functionality via a web page that accesses the control, which can lead to different resultant vulnerabilities, depending on the control's behavior.

Real-world CVEs

3 recorded CVEs are caused by CWE-623 (Unsafe ActiveX Control Marked Safe For Scripting). The highest-severity and most recent are shown first. 0 new CWE-623 CVEs have been recorded so far in 2026 (1 in 2025).

Common consequences

What can happen when CWE-623 is exploited.

Execute Unauthorized Code or Commands

Affects: Confidentiality, Integrity, Availability

How it happens

When it is introduced

Typically introduced during these phases of the software lifecycle.

Architecture and Design

Implementation

Applies to

Technologies

Web Based

How to prevent it

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

Architecture and Design

During development, do not mark it as safe for scripting.

System Configuration

After distribution, you can set the kill bit for the control so that it is not accessible from Internet Explorer.

Illustrative examples

Real CVEs that MITRE cites as examples of this weakness.

CVE-2007-0617 — control allows attackers to add malicious email addresses to bypass spam limits
CVE-2007-0219 — web browser uses certain COM objects as ActiveX
CVE-2006-6510 — kiosk allows bypass to read files

Frequently asked questions

Common questions about CWE-623.

What is CWE-623?: An ActiveX control is intended for restricted use, but it has been marked as safe-for-scripting.
What CVEs are caused by CWE-623?: 3 recorded CVEs are attributed to CWE-623, including CVE-2011-10028, CVE-2014-2368, CVE-2018-17925.
How do you prevent CWE-623?: During development, do not mark it as safe for scripting.
What are the consequences of CWE-623?: Exploiting CWE-623 can lead to: Execute Unauthorized Code or Commands.
Is CWE-623 actively exploited?: 3 recorded CVEs are caused by CWE-623; 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-623

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

Start free See pricing