Answer in brief
CVE-2025-13475 records a Low severity (CVSS 3.5) vulnerability in Cross-Tenant Access via Application Consent Mismanagement in Multiple WSO2 Products Allows Unauthorized Data Exposure. The current sources do not mark it as known exploited. The current feed maps WSO2/WSO2 API Manager (generic), WSO2/WSO2 Identity Server (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 3.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps WSO2/WSO2 API Manager (generic), WSO2/WSO2 Identity Server (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| WSO2/WSO2 API Managergeneric | >=3.2.0 <3.2.0.457 || >=3.2.1 <3.2.1.76 | 3.2.0.457, 3.2.1.76 |
| WSO2/WSO2 Identity Servergeneric | >=5.10.0 <5.10.0.382 | 5.10.0.382 |
Published upstream
Jul 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 9, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 4, 2026
In multi-tenanted deployments, the application consent management mechanism fails to correctly isolate consent scopes between tenants. Consent granted by a user for a specific SaaS application within one tenant can be incorrectly applied to SaaS applications with the same name in other tenants, leading to unintended cross-tenant consent sharing. This vulnerability may result in the exposure of user data across tenants, enabling SaaS applications in different tenants to access and modify information without explicit user authorization. This can lead to unauthorized data access and privacy violations. This vulnerability has no impact if the deployment does not support multi-tenancy.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-13475 records a Low severity (CVSS 3.5) vulnerability in Cross-Tenant Access via Application Consent Mismanagement in Multiple WSO2 Products Allows Unauthorized Data Exposure. The current sources do not mark it as known exploited. The current feed maps WSO2/WSO2 API Manager (generic), WSO2/WSO2 Identity Server (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 3.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps WSO2/WSO2 API Manager (generic), WSO2/WSO2 Identity Server (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| WSO2/WSO2 API Managergeneric | >=3.2.0 <3.2.0.457 || >=3.2.1 <3.2.1.76 | 3.2.0.457, 3.2.1.76 |
| WSO2/WSO2 Identity Servergeneric | >=5.10.0 <5.10.0.382 | 5.10.0.382 |
Published upstream
Jul 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 9, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 4, 2026
In multi-tenanted deployments, the application consent management mechanism fails to correctly isolate consent scopes between tenants. Consent granted by a user for a specific SaaS application within one tenant can be incorrectly applied to SaaS applications with the same name in other tenants, leading to unintended cross-tenant consent sharing. This vulnerability may result in the exposure of user data across tenants, enabling SaaS applications in different tenants to access and modify information without explicit user authorization. This can lead to unauthorized data access and privacy violations. This vulnerability has no impact if the deployment does not support multi-tenancy.
Quoted source text, attributed separately from HOL analysis.