CVE-2025-13475

published 4 Jul 2026 · updated 6 Jul 2026

Cross-Tenant Access via Application Consent Mismanagement in Multiple WSO2 Products Allows Unauthorized Data Exposure

3.5LowCVSS 3.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in API Manager 3.2.0.457, API Manager 3.2.1.76 and Identity Server 5.10.0.382.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
WSO2API Manager>=3.2.0 <3.2.0.457, >=3.2.1 <3.2.1.763.2.0.457, 3.2.1.76
WSO2Identity Server>=5.10.0 <5.10.0.3825.10.0.382

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in WSO2, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2025-13475 severity on Zeptric[![CVE-2025-13475](https://zeptric.io/badge/cve/CVE-2025-13475.svg)](https://zeptric.io/cve/CVE-2025-13475)