# CVE-2024-6423: Sensitive Data Exposure via URL Parameters in Multiple WSO2 Products Allows Confidential Information Leakage


- **Severity:** Medium 4.0 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-x7cg-x993-cw9w

## What is CVE-2024-6423?

CVE-2024-6423 is a medium-severity vulnerability in WSO2 API Manager, published on 21 Oct 2026. 

### Official description

The product failed to enforce validation constraints on user-supplied input in URL parameters, allowing sensitive data to be passed to flows where it was not intended to be processed. Although the product did not utilize this data, its acceptance could lead to logging.

If a user mistakenly sends sensitive data via URL parameters to any flow, this data could be inadvertently logged in access logs. This has the potential to expose confidential information, compromising the security and privacy of affected systems if the product is used incorrectly.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2024-6423 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6423 is a medium-severity vulnerability in WSO2 API Manager, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2024-6423 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-6423/ (Markdown: https://insights.sbomify.com/CVE-2024-6423/index.md)
```

## Sources

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

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