What CVEs are caused by CWE-430?

1 recorded CVEs are attributed to CWE-430, including CVE-2025-3946.

What are the consequences of CWE-430?

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

Is CWE-430 actively exploited?

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

RadicalNotion.AI

Log in Start free

Log in

Log in Start free

Base weakness

Incomplete

CWE-430: Deployment of Wrong Handler

The wrong "handler" is assigned to process an object.

Last updated May 1, 2026

1

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

An example of deploying the wrong handler would be calling a servlet to reveal source code of a .JSP file, or automatically "determining" type of the object even if it is contradictory to an explicitly specified type.

Real-world CVEs

1 recorded CVEs are caused by CWE-430 (Deployment of Wrong Handler). The highest-severity and most recent are shown first. 0 new CWE-430 CVEs have been recorded so far in 2026 (1 in 2025).

CVE-2025-3946
Incorrect response generation during FTEB protocol processing
High · CVSS 8.2 · EPSS 37th
2025-07-10

Common consequences

What can happen when CWE-430 is exploited.

Varies by Context, Unexpected State

Affects: Integrity, 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-430, grouped by where in the lifecycle they apply.

Architecture and Design

Perform a type check before interpreting an object.

Architecture and Design

Reject any inconsistent types, such as a file with a .GIF extension that appears to consist of PHP code.

Illustrative examples

Real CVEs that MITRE cites as examples of this weakness.

CVE-2001-0004 — Source code disclosure via manipulated file extension that causes parsing by wrong DLL.
CVE-2002-0025 — Web browser does not properly handle the Content-Type header field, causing a different application to process the document.
CVE-2000-1052 — Source code disclosure by directly invoking a servlet.
CVE-2002-1742 — Arbitrary Perl functions can be loaded by calling a non-existent function that activates a handler.

Terminology & mappings

Mapped taxonomies

PLOVER: Improper Handler Deployment

Attack patterns

CAPEC attack patterns that exploit this weakness.

CAPEC-11: Cause Web Server Misclassification

Frequently asked questions

Common questions about CWE-430.

What is CWE-430?: The wrong "handler" is assigned to process an object.
What CVEs are caused by CWE-430?: 1 recorded CVEs are attributed to CWE-430, including CVE-2025-3946.
How do you prevent CWE-430?: Perform a type check before interpreting an object.
What are the consequences of CWE-430?: Exploiting CWE-430 can lead to: Varies by Context, Unexpected State.
Is CWE-430 actively exploited?: 1 recorded CVEs are caused by CWE-430; 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-430

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

Start free See pricing