CVE-2024-10302: Improper Input Validation via Signup Process in Multiple WSO2 Products Enables Content Manipulation and Data Exposure
Noroxi assessment
Priority: Monitor (action score 23/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.29% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 6, 2026
- Updated
- Oct 27, 2026
- EPSS
- 0.2% · 21th percentile
- CWE
- CWE-20
Report tools
Action score
23
Monitor
Low priority for now.
- CVSS
- 23 / 40 · 5.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.8
- CNA · WSO2
- 4.0
- 1.8 point gap
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| wso2 | api control plane | cpe:2.3:a:wso2:api_control_plane |
| wso2 | api manager | cpe:2.3:a:wso2:api_manager |
| wso2 | identity server | cpe:2.3:a:wso2:identity_server |
| wso2 | identity server as key manager | cpe:2.3:a:wso2:identity_server_as_key_manager |
| wso2 | open banking iam | cpe:2.3:a:wso2:open_banking_iam |
| wso2 | traffic manager | cpe:2.3:a:wso2:traffic_manager |
| wso2 | universal gateway | cpe:2.3:a:wso2:universal_gateway |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- wso2 api control plane4.5.0
- wso2 api manager3.1.0
- wso2 api manager3.2.0
- wso2 api manager3.2.1
- wso2 api manager4.0.0
- wso2 api manager4.1.0
- wso2 api manager4.2.0
- wso2 api manager4.3.0
- wso2 api manager4.5.0
- wso2 identity server5.10.0
- wso2 identity server5.11.0
- wso2 identity server as key manager5.10.0
- wso2 open banking iam2.0.0
- wso2 traffic manager4.5.0
- wso2 universal gateway4.5.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (WSO2). Independent of NVD's CPE analysis and usually ahead of it.
WSO2 WSO2 API Control Plane
- 4.5.0 and later · before 4.5.0.10affected
WSO2 WSO2 API Manager
- before 3.1.0unknown
- 3.1.0 and later · before 3.1.0.331affected
- 3.2.0 and later · before 3.2.0.427affected
- 3.2.1 and later · before 3.2.1.39affected
- 4.0.0 and later · before 4.0.0.318affected
- 4.1.0 and later · before 4.1.0.200affected
- 4.2.0 and later · before 4.2.0.138affected
- 4.3.0 and later · before 4.3.0.51affected
- 4.5.0 and later · before 4.5.0.9affected
WSO2 WSO2 Carbon Identity Recovery Management
- 1.4.1 and later · before 1.4.1.72affected
- 1.4.72 and later · before 1.4.72.68affected
- 1.4.100 and later · before 1.4.100.8affected
- 1.4.102 and later · before 1.4.102.2affected
- 1.7.2 and later · before 1.7.2.4affected
- 1.8.107 and later · before 1.8.107.2affected
- 1.8.108 and later · before 1.8.108.4affected
- 1.6.380 and later · up to and including 1.6.*not affected
- 1.8.109 and laternot affected
WSO2 WSO2 Identity Server
- before 5.10.0unknown
- 5.10.0 and later · before 5.10.0.358affected
- 5.11.0 and later · before 5.11.0.379affected
WSO2 WSO2 Identity Server as Key Manager
- before 5.10.0unknown
- 5.10.0 and later · before 5.10.0.351affected
WSO2 WSO2 Open Banking IAM
- before 2.0.0unknown
- 2.0.0 and later · before 2.0.0.400affected
WSO2 WSO2 Traffic Manager
- 4.5.0 and later · before 4.5.0.9affected
WSO2 WSO2 Universal Gateway
- 4.5.0 and later · before 4.5.0.9affected
Same product
wso2: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-5430Authentication Bypass via JWT Algorithm Mismatch in Multiple WSO2 Products Allows Account TakeoverKEV77This week
- CVE-2026-1728Privilege Escalation via System REST APIs in Multiple WSO2 Products Permits Admin Account Takeover39Monitor
- CVE-2025-9312Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-8591Jul 6, 2026 · Reflected Cross-Site Scripting via URL Parameter in Multiple WSO2 Products Enables UI Modification24Monitor
- ← EarlierCVE-2026-2445Jul 20, 2026 · Reflected Cross-Site Scripting via URL Parameter in Multiple WSO2 Products Enables UI Redirection and Modification24Monitor
- Later →CVE-2024-6832Aug 6, 2026 · Account Lockout Failure via Secondary User Store Inaccessibility in Multiple WSO2 Products Allows Brute Force Attacks30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.