# CVE-2024-10302: Improper Input Validation via Signup Process in Multiple WSO2 Products Enables Content Manipulation and Data Exposure

> Attackers can inject unvalidated data during user signup, leading to content manipulation and potential data exposure in WSO2 identity products.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-26pj-57w8-hvrq

## What is CVE-2024-10302?

CVE-2024-10302 is a medium-severity vulnerability in Wso2 Api Manager, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2024-10302?

It affects 7 products.


Products: Wso2 Api Control Plane, Wso2 Api Manager, Wso2 Identity Server, Wso2 Identity Server as Key Manager, Wso2 Open Banking Iam, Wso2 Traffic Manager, Wso2 Universal Gateway.

## How do I fix CVE-2024-10302?

No fix has been published for CVE-2024-10302 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-10302 being exploited?

There is no known exploitation of CVE-2024-10302 in the wild and no public exploit code.

## Other vulnerabilities in Wso2 Api Manager

- [CVE-2026-5430](https://insights.sbomify.com/CVE-2026-5430/): WSO2 Multiple Products Path Traversal Vulnerability (critical 10.0, exploited in the wild)
- [CVE-2026-1728](https://insights.sbomify.com/CVE-2026-1728/): Privilege Escalation via System REST APIs in Multiple WSO2 Products Permits Admin Account Takeover (critical 9.8)
- [CVE-2025-9312](https://insights.sbomify.com/CVE-2025-9312/): Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products (critical 9.8)
- [CVE-2025-10611](https://insights.sbomify.com/CVE-2025-10611/): Potential Broken Access Control in Multiple WSO2 Products via System REST APIs (critical 9.8)
- [CVE-2025-9152](https://insights.sbomify.com/CVE-2025-9152/): Improper Privilege Management in Multiple WSO2 API Manager via keymanager-operations DCR Endpoint (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-10302 and fix it if it is affected.

What it is: CVE-2024-10302 is a medium-severity vulnerability in Wso2 Api Manager, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-10302 in the wild and no public exploit code.

Affected product: Wso2 Api Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-10302/ (Markdown: https://insights.sbomify.com/CVE-2024-10302/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-10302
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-10302
- OSV: https://osv.dev/vulnerability/CVE-2024-10302

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-10302/
Summaries are generated and may contain mistakes; the official description above is the record.