Skip to main content
VulnerabilityPublished Updated

CVE-2025-13475: WSO2 Identity Server · Access of Unprotected Resource

Affects WSO2 Identity ServerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.5 Low : upgrade to 5.10.0.382 when convenient.

Data as of 15 Nov 2026, 20:24 UTC

CVSS 3.1 base score
3.5Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.10.0.382, 3.2.1.76, 3.2.0.457
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade WSO2 to 5.10.0.382 (Identity Server); 3.2.1.76 or 3.2.0.457 (API Manager).

Affected software

ProductAffectedFixed in
WSO2WSO2 Identity ServerAffected
  • >=5.10.0 <5.10.0.382
Fixed in
  • 5.10.0.382
WSO2WSO2 API ManagerAffected
  • >=3.2.1 <3.2.1.76
Fixed in
  • 3.2.1.76
WSO2WSO2 API ManagerAffected
  • >=3.2.0 <3.2.0.457
Fixed in
  • 3.2.0.457
Mavenorg.wso2.identity.server/wso2-identity-serverpkg:maven/org.wso2.identity.server/wso2-identity-serverOther threatsAffected
  • =5.10.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, organizations should review their multi-tenant deployment configurations and consider isolating tenants or avoiding use of SaaS applications with identical names across tenants to reduce risk.

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.

References

Community reviews

Loading reviews…