Sensitive Data Exposure via URL Parameters in Multiple WSO2 Products Allows Confidential Information Leakage

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.

Timeline

Scores

EPSS (exploitation in 30 days)

0.10% · top 99% of all CVEs (7 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: no · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.0.

Weakness

• CWE-20: Improper Input Validation (opens in a new tab)All about CWE-20 and its CVEs

Affected products

• WSO2 · WSO2 API Manager

  • unknown < 3.1.0
  • affected 3.1.0 – < 3.1.0.313
  • affected 3.2.0 – < 3.2.0.406
  • affected 3.2.1 – < 3.2.1.30
  • affected 4.0.0 – < 4.0.0.324
  • affected 4.1.0 – < 4.1.0.185
  • affected 4.2.0 – < 4.2.0.124
  • affected 4.3.0 – < 4.3.0.36
  • affected 4.4.0 – < 4.4.0.2

• WSO2 · WSO2 Open Banking AM

  • unknown < 2.0.0
  • affected 2.0.0 – < 2.0.0.363

• WSO2 · WSO2 Identity Server

  • unknown < 5.10.0
  • affected 5.10.0 – < 5.10.0.337
  • affected 5.11.0 – < 5.11.0.384
  • affected 6.0.0 – < 6.0.0.213
  • affected 6.1.0 – < 6.1.0.211
  • affected 7.0.0 – < 7.0.0.50

• WSO2 · WSO2 Identity Server as Key Manager

  • unknown < 5.10.0
  • affected 5.10.0 – < 5.10.0.329

• WSO2 · WSO2 Open Banking IAM

  • unknown < 2.0.0
  • affected 2.0.0 – < 2.0.0.381

• WSO2 · WSO2 Carbon Identity Application

  • affected 6.3.0 – < 6.3.0.18
  • affected 6.3.11 – < 6.3.11.23
  • affected 6.3.58 – < 6.3.58.1
  • affected 6.5.0 – < 6.5.0.5
  • affected 6.6.0 – < 6.6.0.1
  • affected 6.7.8 – < 6.7.8.4
  • affected 6.7.32 – < 6.7.32.1
  • unaffected x – ≤ *

• WSO2 · WSO2 Carbon Identity Core

  • affected 5.17.5 – < 5.17.5.286
  • affected 5.17.118 – < 5.17.118.11
  • affected 5.18.187 – < 5.18.187.263
  • affected 5.18.248 – < 5.18.248.23
  • affected 5.23.8 – < 5.23.8.189
  • affected 5.24.8 – < 5.24.8.12
  • affected 5.25.92 – < 5.25.92.91
  • affected 5.25.92 – < 5.25.92.118
  • affected 5.25.705 – < 5.25.705.11
  • affected 5.25.713 – < 5.25.713.2
  • affected 7.0.78 – < 7.0.78.27
  • unaffected x – ≤ *

• WSO2 · WSO2 Carbon Identity Oauth

  • affected 6.4.2 – < 6.4.2.142
  • affected 6.4.176 – < 6.4.176.20
  • affected 6.4.180 – < 6.4.180.8
  • affected 6.8.0 – < 6.8.0.40
  • affected 6.9.6 – < 6.9.6.16
  • affected 6.11.21 – < 6.11.21.44
  • affected 6.13.16 – < 6.13.16.6
  • affected 6.13.19 – < 6.13.19.2
  • affected 7.0.26 – < 7.0.26.18

What to do

Solution: Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3465/#solution

References (1)

• https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2024-3465/ (opens in a new tab)vendor-advisory

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2024-6423](https://trackcve.app/badge/CVE-2024-6423.svg)](https://trackcve.app/cve/CVE-2024-6423)

Record last updated 30 Oct 2026, 15:11 UTC.