Description
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 products
wso2: api manager; wso2: identity server
References1
- security.docs.wso2.com/en/latest/security-announcements/securit… Vendor Advisory
Metrics
- CVSS 3.1
-
7.3
HIGH
Score source: NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N - EPSS — exploit probability
- 0% percentile: 20 · as of 16 November 2026
- CWE
- CWE-288
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.