Information Disclosure in Multiple WSO2 Products Allows Exposure of Certificate File Paths
Affects WSO2 Identity Server 5.10.0 through 7.2.0, WSO2 Identity Server as Key Manager 5.10.0, WSO2 Open Banking IAM 2.0.0, and the Keystore REST API components. Fixed in builds such as 7.2.0.3 for the 7.2.0 line.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.10.0.381, 5.11.0.428, 6.0.0.255, 6.1.0.255, 7.0.0.133, and 11 more
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 5.10.0.381, 5.11.0.428, 6.0.0.255, 6.1.0.255, 7.0.0.133, or one of 11 more.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 5.10.0.381, 5.11.0.428, 6.0.0.255, 6.1.0.255, 7.0.0.133, and 11 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
The vulnerability affects multiple WSO2 products, where a flaw in how certain requests are validated allows crafted Content-Type headers to be processed improperly. Successful exploitation could reveal file system paths to certificate files, which could aid further attacks or weaken the confidentiality of the system.
Read the original description
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.
What to do
Upgrade to a fixed version: 5.10.0.381, 5.11.0.428, 6.0.0.255, 6.1.0.255, 7.0.0.133, or one of 11 more.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- WSO2 WSO2 Identity Server
From 5.10.0 · fixed in 5.10.0.381; From 5.11.0 · fixed in 5.11.0.428; From 6.0.0 · fixed in 6.0.0.255; From 6.1.0 · fixed in 6.1.0.255; From 7.0.0 · fixed in 7.0.0.133; From 7.1.0 · fixed in 7.1.0.41; From 7.2.0 · fixed in 7.2.0.3
- WSO2 WSO2 Open Banking IAM
From 2.0.0 · fixed in 2.0.0.421
- WSO2 WSO2 Identity Server as Key Manager
From 5.10.0 · fixed in 5.10.0.372
- org.wso2.carbon.identity.api.server.keystore.management.common
From 1.0.82 · fixed in 1.0.82.25; From 1.0.190 · fixed in 1.0.190.17; From 1.2.3 · fixed in 1.2.3.6; From 1.2.23 · fixed in 1.2.23.10; From 1.2.176 · fixed in 1.2.176.18; From 1.3.83 · fixed in 1.3.83.10; From 1.3.213 · fixed in 1.3.213.1
- org.wso2.carbon.identity.server.api:org.wso2.carbon.identity.api.server.keystore.management.v1
From 1.0.82 · fixed in 1.0.82.25; From 1.0.190 · fixed in 1.0.190.17; From 1.2.3 · fixed in 1.2.3.6; From 1.2.23 · fixed in 1.2.23.10; From 1.2.176 · fixed in 1.2.176.18; From 1.3.83 · fixed in 1.3.83.10; From 1.3.213 · fixed in 1.3.213.1
Evidence 1
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2025-13647
What does this mean?
The flaw lets the server disclose the file paths of certificate files. The advisory says this could facilitate further attacks or compromise confidentiality.Source: security.docs.wso2.com
Am I affected, and how do I check?
The advisory lists WSO2 Identity Server 5.10.0, 5.11.0, 6.0.0, 6.1.0, 7.0.0, 7.1.0 and 7.2.0 before their fixed builds, WSO2 Identity Server as Key Manager 5.10.0, WSO2 Open Banking IAM 2.0.0, and the Keystore REST API Commons and V1 components in the listed ranges. To check a version, look at the product version shown in the admin console or the installed build number.Source: security.docs.wso2.com
What should I do about it?
Upgrade to the fixed build for the release line in use, as listed in the advisory, for example 7.2.0.3 for the 7.2.0 line or 6.1.0.255 for the 6.1.0 line.Source: security.docs.wso2.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data