Skip to content
Fencer Vulns
medium 5.8

CVE-2025-13647 json

Information Disclosure in Multiple WSO2 Products Allows Exposure of Certificate File Paths

published 2026-11-02 7 d ago modified 2026-11-04 4 d ago also EUVD-2025-211234

cvss
5.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 7%
public exploits
0
none known

Summary

The affected component fails to enforce expected validation constraints on the `content-type` header when processing certain requests. This allows an attacker to submit a crafted request with a manipulated `content-type` header.

Successful exploitation can lead to the unintended exposure of the file paths for certificate files. This information disclosure could potentially be leveraged in subsequent attacks or compromise the confidentiality of the system.

Patch / fix

  • WSO2 WSO2 Identity Server 5.10.0.381, 5.11.0.428, 6.0.0.255, 6.1.0.255, 7.0.0.133, 7.1.0.41, 7.2.0.3
  • WSO2 WSO2 Open Banking IAM 2.0.0.421
  • WSO2 WSO2 Identity Server as Key Manager 5.10.0.372
  • WSO2 WSO2 Identity Server Keystore Rest API Commons 1.0.82.25, 1.0.190.17, 1.2.3.6, 1.2.23.10, 1.2.176.18, 1.3.83.10, 1.3.213.1, 1.3.221
  • WSO2 WSO2 Identity Server Keystore Rest API V1 1.0.82.25, 1.0.190.17, 1.2.3.6, 1.2.23.10, 1.2.176.18, 1.3.83.10, 1.3.213.1, 1.3.221

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
6 d ago

Exploit prediction

0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

Affected products

  • WSO2 WSO2 Identity Server
  • WSO2 WSO2 Open Banking IAM
  • WSO2 WSO2 Identity Server as Key Manager
  • WSO2 WSO2 Identity Server Keystore Rest API Commons
  • WSO2 WSO2 Identity Server Keystore Rest API V1

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.