What CVEs are caused by CWE-233?

31 recorded CVEs are attributed to CWE-233, including CVE-2024-24525, CVE-2022-45182, CVE-2026-32998.

What are the consequences of CWE-233?

Exploiting CWE-233 can lead to: Unexpected State.

Is CWE-233 actively exploited?

31 recorded CVEs are caused by CWE-233; 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-233: Improper Handling of Parameters

The product does not properly handle when the expected number of parameters, fields, or arguments is not provided in input, or if those parameters are undefined.

Last updated May 1, 2026

31

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-233 (Improper Handling of Parameters) 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

31 recorded CVEs are caused by CWE-233 (Improper Handling of Parameters). The highest-severity and most recent are shown first. 7 new CWE-233 CVEs have been recorded so far in 2026 (3 in 2025).

Improper Handling of Parameters in GitLab

High · CVSS 8.8 · EPSS 35th

2026-03-29

CVE-2024-31808

High · CVSS 8.8 · EPSS 56th

2024-04-08

CVE-2023-20076

High · CVSS 8.8 · EPSS 71th

2023-02-12

CVE-2021-0269

Junos OS: J-Web can be compromised through reflected client-side HTTP parameter pollution attacks.

High · CVSS 8.8 · EPSS 55th

2021-04-22

CVE-2023-20514

High · CVSS 8.7 · EPSS 4th

2026-02-11

CVE-2021-1230

High · CVSS 8.6 · EPSS 71th

2021-02-24

CVE-2023-7261

High · CVSS 7.8 · EPSS 6th

2024-06-07

CVE-2025-52970

High · CVSS 7.7 · EPSS 95th

2025-08-12

CVE-2023-26549

High · CVSS 7.5 · EPSS 34th

2023-03-27

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

Monitor CWE-233 vulnerabilities

Common consequences

What can happen when CWE-233 is exploited.

Unexpected State

Affects: Integrity

How it happens

When it is introduced

Typically introduced during these phases of the software lifecycle.

Implementation

How to detect it

Fuzzing

Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.

Effectiveness: High

Automated Static Analysis

Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

Effectiveness: High

Code examples

Illustrative examples from MITRE showing how the weakness appears in code.

This Android application has registered to handle a URL when sent an intent:

The application assumes the URL will always be included in the intent. When the URL is not present, the call to getStringExtra() will return null, thus causing a null pointer exception when length() is called.

Terminology & mappings

Mapped taxonomies

PLOVER: Parameter Problems

Attack patterns

CAPEC attack patterns that exploit this weakness.

CAPEC-39: Manipulating Opaque Client-based Data Tokens

Frequently asked questions

Common questions about CWE-233.

What is CWE-233?: The product does not properly handle when the expected number of parameters, fields, or arguments is not provided in input, or if those parameters are undefined.
What CVEs are caused by CWE-233?: 31 recorded CVEs are attributed to CWE-233, including CVE-2024-24525, CVE-2022-45182, CVE-2026-32998.
How is CWE-233 detected?: Fuzzing: Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.
What are the consequences of CWE-233?: Exploiting CWE-233 can lead to: Unexpected State.
Is CWE-233 actively exploited?: 31 recorded CVEs are caused by CWE-233; 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-233

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

Start free See pricing