What CVEs are caused by CWE-351?

14 recorded CVEs are attributed to CWE-351, including CVE-2023-38831, CVE-2025-30510, CVE-2025-54413. 1 are listed in CISA's Known Exploited Vulnerabilities (KEV) catalog.

What are the consequences of CWE-351?

Exploiting CWE-351 can lead to: Other.

Is CWE-351 actively exploited?

Yes. 1 CWE-351 vulnerabilities are in CISA's KEV catalog of actively exploited flaws, out of 14 recorded CVEs.

RadicalNotion.AI

Log in Start free

Log in

Log in Start free

Base weakness

Draft

CWE-351: Insufficient Type Distinction

The product does not properly distinguish between different types of elements in a way that leads to insecure behavior.

Last updated May 1, 2026

14

Recorded CVEs

With this primary weakness

1

KEVs

In the CISA KEV catalog

Not rated

Likelihood of exploit

Per MITRE

Base

Abstraction

MITRE classification

Overview

CWE-351 (Insufficient Type Distinction) 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

14 recorded CVEs are caused by CWE-351 (Insufficient Type Distinction), including 1 in CISA's KEV (Known Exploited Vulnerabilities) catalog. KEVs are shown first. 2 new CWE-351 CVEs have been recorded so far in 2026 (6 in 2025).

High · CVSS 8.7 · EPSS 4th

2025-07-26

CVE-2025-54412

skops' Inconsistent Trusted Type Validation Enables Hidden `operator` Methods Execution

High · CVSS 8.7 · EPSS 4th

2025-07-26

CVE-2023-2866

High · CVSS 7.8 · EPSS 4th

2023-06-07

CVE-2025-32035

DNN does not check the contents of a file when uploading files

High · CVSS 7.5 · EPSS 7th

2025-04-08

CVE-2022-1642

High · CVSS 7.5 · EPSS 45th

2022-06-16

CVE-2025-65960

Contao is vulnerable to remote code execution in template closures

Medium · CVSS 6.6 · EPSS 5th

2025-11-25

CVE-2026-15305

TYPO3 CMS - Unrestricted File Upload in Form Framework

Medium · CVSS 6.3 · EPSS 7th

2026-07-14

CVE-2020-10134

Medium · CVSS 6.3 · EPSS 47th

2020-05-19

CVE-2024-4769

Medium · CVSS 5.9 · EPSS 29th

2024-05-14

CVE-2025-47939

TYPO3 CMS Vulnerable to Unrestricted File Upload in File Abstraction Layer

Medium · CVSS 5.4 · EPSS 5th

2025-05-20

Showing 12 of 14 recorded CWE-351 CVEs. Track new ones as they are published and get AI-written analysis and fixes.

Monitor CWE-351 vulnerabilities

Common consequences

What can happen when CWE-351 is exploited.

Other

Affects: Other

How it happens

When it is introduced

Typically introduced during these phases of the software lifecycle.

Implementation

Illustrative examples

Real CVEs that MITRE cites as examples of this weakness.

CVE-2005-2260 — Browser user interface does not distinguish between user-initiated and synthetic events.
CVE-2005-2801 — Product does not compare all required data in two separate elements, causing it to think they are the same, leading to loss of ACLs. Similar to Same Name error.

Terminology & mappings

Mapped taxonomies

PLOVER: Insufficient Type Distinction

Frequently asked questions

Common questions about CWE-351.

What is CWE-351?: The product does not properly distinguish between different types of elements in a way that leads to insecure behavior.
What CVEs are caused by CWE-351?: 14 recorded CVEs are attributed to CWE-351, including CVE-2023-38831, CVE-2025-30510, CVE-2025-54413. 1 are listed in CISA's Known Exploited Vulnerabilities (KEV) catalog.
What are the consequences of CWE-351?: Exploiting CWE-351 can lead to: Other.
Is CWE-351 actively exploited?: Yes. 1 CWE-351 vulnerabilities are in CISA's KEV catalog of actively exploited flaws, out of 14 recorded CVEs.

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-351

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

Start free See pricing