CyberSecBulletin
CVE-2025-13475NVD status: Analyzed

WSO2 Identity Server: Authentication Bypass Using an Alternate Path or Channel

CVE-2025-13475 is a high-severity authentication bypass using an alternate path or channel vulnerability in WSO2 Identity Server from WSO2, with a CVSS 3.1 base score of 7.3 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, but only if a user takes part, for example by opening a link or file. The record lists version 5.10.0.382 as the first without the flaw, so updating WSO2 Identity Server to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.27% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update WSO2 Identity Server to 5.10.0.382 or a later version.
  2. Update WSO2 API Manager to 3.2.0.457 or 3.2.1.76, whichever matches your release line, or a later version.
  3. Update API Manager to 3.2.0.457 or 3.2.1.76, whichever matches your release line, or a later version.
  4. Read the advisory on security.docs.wso2.com for workarounds and exact fixed builds.
  5. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

VendorProductAffected versionsFixed in
WSO2WSO2 Identity Server5.10.0 up to, but not including, 5.10.0.3825.10.0.382
WSO2WSO2 API Manager3.2.0 up to, but not including, 3.2.0.457; 3.2.1 up to, but not including, 3.2.1.763.2.0.457, 3.2.1.76
WSO2API Manager3.2.0 up to, but not including, 3.2.0.457; 3.2.1 up to, but not including, 3.2.1.763.2.0.457, 3.2.1.76
WSO2Identity Server5.10.0 up to, but not including, 5.10.0.3825.10.0.382

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
RequiredA user must take an action such as opening a file or link.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.13.5LowCNA
CVSS 3.17.3HighNVD

Official 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Authentication Bypass Using an Alternate Path or Channel

The product requires authentication, but the product has an alternate path or channel that does not require authentication.

How developers prevent this class of flaw

  • Funnel all access through a single choke point to simplify how users can access a resource. For every access, perform a check to determine if the user has permissions to access the resource.

More Authentication Bypass Using an Alternate Path or Channel vulnerabilities (CWE-288)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in WSO2 Identity Server

All WSO2 Identity Server vulnerabilities

Recent Authentication Bypass Using an Alternate Path or Channel vulnerabilities

Spotted an error? Tell us.