CVE Intelligence
Medium Input validation

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

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.

Published Oct 21, 2026 · Updated Oct 21, 2026 · Sources: CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database · CNA: WSO2

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.1% (30-day exploitation probability)+0
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.1%
ahead of 1% of scored CVEs · Oct 23, 2026
Affects
WSO2
Api Manager and 7 more
CVSS base
4.0
Medium · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (WSO2 Api Manager, WSO2 Identity Server, WSO2 Identity Server As Key Manager…).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  4. Search available logs for exploit probes matching the vulnerability class (input validation), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
WSO2 Api Manager ≥ 3.2.0 and < 3.2.0.406≥ 3.2.1 and < 3.2.1.30≥ 4.0.0 and < 4.0.0.324≥ 4.1.0 and < 4.1.0.185≥ 4.2.0 and < 4.2.0.124≥ 4.3.0 and < 4.3.0.36≥ 4.4.0 and < 4.4.0.2≥ 3.1.0 and < 3.1.0.313 Vulnerable CVE Program (cve.org) e CISA ADP
WSO2 Identity Server ≥ 5.11.0 and < 5.11.0.384≥ 7.0.0 and < 7.0.0.50≥ 6.1.0 and < 6.1.0.211≥ 6.0.0 and < 6.0.0.213≥ 5.10.0 and < 5.10.0.337 Vulnerable CVE Program (cve.org) e CISA ADP
WSO2 Identity Server As Key Manager ≥ 5.10.0 and < 5.10.0.329 Vulnerable CVE Program (cve.org) e CISA ADP
WSO2 Open Banking Am ≥ 2.0.0 and < 2.0.0.363 Vulnerable CVE Program (cve.org) e CISA ADP
WSO2 Open Banking Iam ≥ 2.0.0 and < 2.0.0.381 Vulnerable CVE Program (cve.org) e CISA ADP
WSO2 WSO2 Carbon Identity Application ≥ 6.7.8 and < 6.7.8.4≥ 6.7.32 and < 6.7.32.1≥ 6.6.0 and < 6.6.0.1≥ 6.3.58 and < 6.3.58.1≥ 6.3.11 and < 6.3.11.23≥ 6.3.0 and < 6.3.0.18≥ 6.5.0 and < 6.5.0.5 Vulnerable CVE Program (cve.org) e CISA ADP
WSO2 WSO2 Carbon Identity Core ≥ 5.25.705 and < 5.25.705.11≥ 7.0.78 and < 7.0.78.27≥ 5.25.713 and < 5.25.713.2≥ 5.25.92 and < 5.25.92.118≥ 5.25.92 and < 5.25.92.91≥ 5.24.8 and < 5.24.8.12≥ 5.23.8 and < 5.23.8.189≥ 5.18.248 and < 5.18.248.23
and 3 more ≥ 5.18.187 and < 5.18.187.263≥ 5.17.118 and < 5.17.118.11≥ 5.17.5 and < 5.17.5.286
Vulnerable CVE Program (cve.org) e CISA ADP
WSO2 WSO2 Carbon Identity Oauth ≥ 6.4.2 and < 6.4.2.142≥ 6.4.176 and < 6.4.176.20≥ 6.4.180 and < 6.4.180.8≥ 6.8.0 and < 6.8.0.40≥ 6.9.6 and < 6.9.6.16≥ 6.11.21 and < 6.11.21.44≥ 6.13.16 and < 6.13.16.6≥ 6.13.19 and < 6.13.19.2
and 1 more ≥ 7.0.26 and < 7.0.26.18
Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
High
Privileges required
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
4.0 CVSS 3.1 Medium 0.3 3.6 ed10eef1-636d-4fbe-9993-6890dfa878f8 via NIST National Vulnerability Database
4.0 CVSS 3.1 Medium — — WSO2 via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:N/A:N (score shown at the top: ed10eef1-636d-4fbe-9993-6890dfa878f8)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-20 · Improper Input Validation

Other CVEs with this weakness →

EPSS over time FIRST

Oct 22, 2026 → Oct 23, 2026 · 2 reading(s) · max 0.10%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Received → Awaiting Analysis
    Oct 21, 2026 · NIST National Vulnerability Database
  • Source status changed · Published → Received
    Oct 21, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 21, 2026
  • CVSS changed · 4.0
    Oct 21, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 21, 2026 · CVE Program (cve.org) e CISA ADP
  • Record created in this database
    Oct 21, 2026 · CVE Program (cve.org) e CISA ADP
  • CVE published
    Oct 21, 2026 · WSO2

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 21, 2026 – Oct 21, 2026

References

1 on the record

Elsewhere on this site

WSO2
every CVE for this vendor
CWE-20
other pages naming this weakness

Related CVEs (same products)

  • Unknown CVE-2025-0326 Improper Token Revocation in WSO2 Identity Server Allows Unauthorized Access 3d
  • Medium CVE-2024-7478 Username Enumeration via External User Stores in Multiple WSO2 Products Allows User Account Discovery 3d
  • Medium CVE-2024-5563 Incomplete reCaptcha Implementation in Authentication Flows in WSO2 Identity Server Allows Brute Force Attacks 3d
  • Medium CVE-2024-5139 Cross-Site Scripting via Authentication Endpoint in Multiple WSO2 Products Enables UI Manipulation and Redirection 3d
  • Medium CVE-2024-4989 Open Redirection via Callback URL in WSO2 API Manager Allows Phishing Attacks 3d
  • Medium CVE-2024-2323 Password Brute Force via Password History Validation in Multiple WSO2 Products Allows User Account Discovery 4d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2024-6423 is "Sensitive Data Exposure via URL Parameters in Multiple WSO2 Products Allows Confidential Information Leakage", rated Medium. It affects Api Manager (WSO2); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.0 describes technical severity. EPSS 0.10% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.