WSO2 Identity Server
CVE-2025-13647
MEDIUM
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exposed WSO2 keystore REST endpoint
-
DeliverySend request with manipulated content-type header
-
ExploitBypass content-type validation constraints
-
ExecutionTrigger disclosure of certificate file paths
-
ImpactCollect paths for follow-on attacks
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network access to an exposed WSO2 keystore REST API endpoint (the Keystore REST API commons/v1 components) and the ability to send a request carrying a manipulated content-type header that the component fails to validate; per the CVSS vector (PR:N) no authentication is indicated. What limits impact: the outcome is confined to disclosure of certificate file paths - not file contents, keys, or credentials - so the flaw yields reconnaissance data rather than direct access, and its usefulness depends on the attacker being able to reach the affected API over the network. The exact triggering content-type value and whether non-default configuration is required are not described in the available sources. |
| Impact | This is a moderate-severity information-disclosure issue, not an urgent priority. The supplied CVSS vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N, base 5.8) indicates a network-reachable, low-complexity, unauthenticated flaw with only a low confidentiality impact and no integrity or availability impact - consistent with disclosure of certificate file paths rather than file contents or credentials. The vuln.today decision label is 'this_month,' signaling a routine patch cadence rather than emergency action. No EPSS score, no CISA KEV listing, and no POC or exploit reference are present in the input, so there is no public evidence of active or imminent exploitation. The scope-change flag (S:C) in the input raises the score modestly, but the actual harm is limited: leaked filesystem paths to certificate files are reconnaissance value that could aid subsequent attacks, not a direct compromise. Overall this is a genuine but low-to-moderate priority finding - patch on a normal maintenance schedule; it is not a high-CVSS-but-illusory issue, nor is it an emergency. |
| Exploit ScenarioDerived | A remote attacker sends a crafted HTTP request to an exposed WSO2 Identity Server keystore REST API endpoint with a manipulated content-type header that evades the expected validation. The weak validation causes the application to return an error or response that reveals the server-side file paths of certificate files, which the attacker records for use in later, more targeted attacks. No public exploit code or POC reference is provided in the available sources. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 02, 2026
Information disclosure in WSO2 Identity Server's Keystore REST API lets remote attackers learn the server-side file paths of certificate files by sending a request whose content-type header the component fails to validate. The affected code spans the Keystore REST API commons and v1 modules, and the same component ships in WSO2 Identity Server, Identity Server as Key Manager and Open Banking IAM. The exposure is limited to path strings rather than certificate contents, private keys or credentials, and no public exploit has been identified at time of analysis; the vendor rated it 5.8 with Scope:Changed, while the independent assessment treats scope as unchanged and scores confidentiality-only, low impact.
RemediationAI
No fixed version is stated in the available data, so the primary action is to consult vendor advisory WSO2-2025-4751 (https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4751/) for the patched release and upgrade path, and to apply it across every affected deployment - Identity Server, Identity Server as Key Manager, Open Banking IAM and the Keystore REST API commons and v1 modules. Until that update is in place, the exposure can be reduced by restricting network reachability of the keystore REST API endpoints, since exploitation requires the attacker to be able to send requests to an exposed endpoint; the trade-off is that legitimate programmatic keystore operations from the segments you cut off will stop working. The exact triggering content-type value is not described in the available sources, so a targeted header-filtering rule cannot be reliably derived from the published information, and header-based blocking should be treated as unverified rather than as a substitute for the vendor fix.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is classified as CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) and sits in the WSO2 Carbon keystore REST API layer - the CPE data names both a commons module and a v1 API module distributed with WSO2 Identity Server, Identity Server as Key Manager and Open Banking IAM. Rather than deriving a path from the request in a controlled way, the affected component fails to enforce the validation constraints it is expected to apply to the content-type header, so a crafted request carrying a manipulated content-type reaches a code path that returns certificate file locations in its response. The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates the issue is reachable over the network with no authentication or user interaction indicated, and the only impacted property is confidentiality at low severity - integrity and availability are untouched. The independent assessment uses Scope:Unchanged, reflecting that the leaked data is limited to path strings, whereas the vendor's Scope:Changed vector yields the 5.8 score. What the available sources do not describe is the exact content-type value that triggers the behaviour and whether any non-default configuration is required; the trigger mechanism itself is not documented beyond the missing header validation.
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
Remote unauthenticated request via a malformed content-type header (AV:N/AC:L/PR:N/UI:N); only low confidentiality from path disclosure, no integrity/availability impact, and no cross-component boundary crossed (S:U).
Primary rating from Vendor (WSO2).
CVSS VectorVendor: WSO2
DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Affected Products (CPE)CVE.org
More in Wso2 Identity Server
View allAuthentication bypass in WSO2 Identity Server and multiple WSO2 platform products (API Manager, Open Banking AM/IAM/KM,
Memory exhaustion denial-of-service in WSO2 Identity Server's Magic Link authenticator allows remote unauthenticated att
OS command injection (CWE-78) in WSO2's shared Carbon Console administrative interface allows an authenticated administr
Server-side request forgery in WSO2 API Manager and related WSO2 products lets a remote attacker direct the server to ar
The SCIM provisioning endpoints in WSO2 Identity Server, Identity Server as Key Manager, and Open Banking IAM fail to di
The XML parsers within multiple WSO2 products accept user-supplied XML data without properly configuring to prevent the
OAuth token revocation in WSO2 Identity Server fails to invalidate access and refresh tokens for accounts whose username
Previously issued OAuth access tokens for sub-organization users remain valid in WSO2 Identity Server 7.0.0 before 7.0.0
Account-lockout bypass in WSO2 Identity Server (6.0.0, 6.1.0, 7.0.0, 7.1.0) and the Carbon MagicLink Authenticator Modul
Adaptive authentication flows in WSO2 Identity Server 7.1.0 (up to 7.1.0.26) and the Conditional Authentication User and
WSO2 Carbon OAuth, as shipped in WSO2 Identity Server, API Manager, and related WSO2 products, can leave session-bound t
Reflected cross-site scripting (CWE-79) affects WSO2's authentication endpoint, which echoes unsanitized request data in
NVD
CVE.org
GitHub PoC
Exploit-DB