cve.bz

CVE-2024-10302 wso2: Improper Input Validation

5.8 mediumEPSS 0.3%Fix available

Medium (5.8) in wso2. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

5.8 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 22nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-20 Improper Input Validation
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Under analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-10302 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-10302?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-10302?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-10302 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
WSO2 API Control Planefrom 4.5.0 before 4.5.0.10
WSO2 Traffic Managerfrom 4.5.0 before 4.5.0.9
WSO2 Universal Gatewayfrom 4.5.0 before 4.5.0.9
WSO2 API Managerfrom 3.1.0 before 3.1.0.331
WSO2 API Managerfrom 3.2.0 before 3.2.0.427
WSO2 API Managerfrom 3.2.1 before 3.2.1.39
WSO2 API Managerfrom 4.0.0 before 4.0.0.318
WSO2 API Managerfrom 4.1.0 before 4.1.0.200
WSO2 API Managerfrom 4.2.0 before 4.2.0.138
WSO2 API Managerfrom 4.3.0 before 4.3.0.51
WSO2 API Managerfrom 4.5.0 before 4.5.0.9
WSO2 Open Banking IAMfrom 2.0.0 before 2.0.0.400
WSO2 Identity Server as Key Managerfrom 5.10.0 before 5.10.0.351
WSO2 Identity Serverfrom 5.10.0 before 5.10.0.358
WSO2 Identity Serverfrom 5.11.0 before 5.11.0.379
WSO2 Carbon Identity Recovery Managementfrom 1.4.1 before 1.4.1.72
WSO2 Carbon Identity Recovery Managementfrom 1.4.72 before 1.4.72.68
WSO2 Carbon Identity Recovery Managementfrom 1.4.100 before 1.4.100.8
WSO2 Carbon Identity Recovery Managementfrom 1.4.102 before 1.4.102.2
WSO2 Carbon Identity Recovery Managementfrom 1.7.2 before 1.7.2.4
WSO2 Carbon Identity Recovery Managementfrom 1.8.107 before 1.8.107.2
WSO2 Carbon Identity Recovery Managementfrom 1.8.108 before 1.8.108.4

Fixed in

ProductRelease lineFixed in
WSO2 Carbon Identity Recovery Management1.61.6.380
WSO2 Carbon Identity Recovery Managementlater releases1.8.109

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON