Answer in brief
CVE-2024-10302 records a Medium severity (CVSS 4.0) vulnerability in Improper Input Validation via Signup Process in Multiple WSO2 Products Enables Content Manipulation and Data Exposure. The current sources do not mark it as known exploited. The current feed maps WSO2/WSO2 API Control Plane (generic), WSO2/WSO2 API Manager (generic), WSO2/WSO2 Carbon Identity Recovery Management (generic), WSO2/WSO2 Identity Server (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 4.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps WSO2/WSO2 API Control Plane (generic), WSO2/WSO2 API Manager (generic), WSO2/WSO2 Carbon Identity Recovery Management (generic), WSO2/WSO2 Identity Server (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| WSO2/WSO2 API Control Planegeneric | >=4.5.0 <4.5.0.10 | 4.5.0.10 |
| WSO2/WSO2 API Managergeneric | >=3.1.0 <3.1.0.331 || >=3.2.0 <3.2.0.427 || >=3.2.1 <3.2.1.39 || >=4.0.0 <4.0.0.318 || >=4.1.0 <4.1.0.200 || >=4.2.0 <4.2.0.138 || >=4.3.0 <4.3.0.51 || >=4.5.0 <4.5.0.9 | 3.1.0.331, 3.2.0.427, 3.2.1.39, 4.0.0.318, 4.1.0.200, 4.2.0.138, 4.3.0.51, 4.5.0.9 |
| WSO2/WSO2 Carbon Identity Recovery Managementgeneric | >=1.4.1 <1.4.1.72 || >=1.4.72 <1.4.72.68 || >=1.4.100 <1.4.100.8 || >=1.4.102 <1.4.102.2 || >=1.7.2 <1.7.2.4 || >=1.8.107 <1.8.107.2 || >=1.8.108 <1.8.108.4 | 1.4.1.72, 1.4.72.68, 1.4.100.8, 1.4.102.2, 1.7.2.4, 1.8.107.2, 1.8.108.4 |
| WSO2/WSO2 Identity Servergeneric | >=5.10.0 <5.10.0.358 || >=5.11.0 <5.11.0.379 | 5.10.0.358, 5.11.0.379 |
| WSO2/WSO2 Identity Server as Key Managergeneric | >=5.10.0 <5.10.0.351 | 5.10.0.351 |
| WSO2/WSO2 Open Banking IAMgeneric | >=2.0.0 <2.0.0.400 | 2.0.0.400 |
| WSO2/WSO2 Traffic Managergeneric | >=4.5.0 <4.5.0.9 | 4.5.0.9 |
| WSO2/WSO2 Universal Gatewaygeneric | >=4.5.0 <4.5.0.9 | 4.5.0.9 |
Published upstream
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 6, 2026
The user self-signup flow in multiple WSO2 products fails to adequately validate user-supplied input. This weakness allows arbitrary unvalidated data to be included within user claims, which are then used by downstream processes. Allowing unvalidated input into user claims can lead to various security risks. Malicious or malformed data injected during signup could be processed by other parts of the application, potentially enabling attacks such as content manipulation, redirection, user interface inconsistencies, unauthorized actions, and data exposure. The actual impact depends on how the compromised data is consumed and the privileges associated with the affected users.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-10302 records a Medium severity (CVSS 4.0) vulnerability in Improper Input Validation via Signup Process in Multiple WSO2 Products Enables Content Manipulation and Data Exposure. The current sources do not mark it as known exploited. The current feed maps WSO2/WSO2 API Control Plane (generic), WSO2/WSO2 API Manager (generic), WSO2/WSO2 Carbon Identity Recovery Management (generic), WSO2/WSO2 Identity Server (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 4.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps WSO2/WSO2 API Control Plane (generic), WSO2/WSO2 API Manager (generic), WSO2/WSO2 Carbon Identity Recovery Management (generic), WSO2/WSO2 Identity Server (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| WSO2/WSO2 API Control Planegeneric | >=4.5.0 <4.5.0.10 | 4.5.0.10 |
| WSO2/WSO2 API Managergeneric | >=3.1.0 <3.1.0.331 || >=3.2.0 <3.2.0.427 || >=3.2.1 <3.2.1.39 || >=4.0.0 <4.0.0.318 || >=4.1.0 <4.1.0.200 || >=4.2.0 <4.2.0.138 || >=4.3.0 <4.3.0.51 || >=4.5.0 <4.5.0.9 | 3.1.0.331, 3.2.0.427, 3.2.1.39, 4.0.0.318, 4.1.0.200, 4.2.0.138, 4.3.0.51, 4.5.0.9 |
| WSO2/WSO2 Carbon Identity Recovery Managementgeneric | >=1.4.1 <1.4.1.72 || >=1.4.72 <1.4.72.68 || >=1.4.100 <1.4.100.8 || >=1.4.102 <1.4.102.2 || >=1.7.2 <1.7.2.4 || >=1.8.107 <1.8.107.2 || >=1.8.108 <1.8.108.4 | 1.4.1.72, 1.4.72.68, 1.4.100.8, 1.4.102.2, 1.7.2.4, 1.8.107.2, 1.8.108.4 |
| WSO2/WSO2 Identity Servergeneric | >=5.10.0 <5.10.0.358 || >=5.11.0 <5.11.0.379 | 5.10.0.358, 5.11.0.379 |
| WSO2/WSO2 Identity Server as Key Managergeneric | >=5.10.0 <5.10.0.351 | 5.10.0.351 |
| WSO2/WSO2 Open Banking IAMgeneric | >=2.0.0 <2.0.0.400 | 2.0.0.400 |
| WSO2/WSO2 Traffic Managergeneric | >=4.5.0 <4.5.0.9 | 4.5.0.9 |
| WSO2/WSO2 Universal Gatewaygeneric | >=4.5.0 <4.5.0.9 | 4.5.0.9 |
Published upstream
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 6, 2026
The user self-signup flow in multiple WSO2 products fails to adequately validate user-supplied input. This weakness allows arbitrary unvalidated data to be included within user claims, which are then used by downstream processes. Allowing unvalidated input into user claims can lead to various security risks. Malicious or malformed data injected during signup could be processed by other parts of the application, potentially enabling attacks such as content manipulation, redirection, user interface inconsistencies, unauthorized actions, and data exposure. The actual impact depends on how the compromised data is consumed and the privileges associated with the affected users.
Quoted source text, attributed separately from HOL analysis.