# CVE-2025-1397: WSO2 Access token issuance without IDP status validation

Source: https://junglewise.ai/threats/cve-2025-1397-when-utilizing-jwt-bearer-or-saml2-bearer-grant-types-the-system  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-03. Updated: 2026-11-03  
License: CC BY 4.0 with a link back

CVE-2025-1397 · Severity: medium · CVSS 4.8 · Published 2026-11-03

WSO2's identity management system fails to check whether an Identity Provider has been disabled before issuing access tokens through JWT Bearer or SAML2 Bearer authentication methods. An attacker could exploit this to obtain access tokens from a disabled IDP and gain unauthorized access to protected resources that should be blocked.

Technologies: [Wso2 Identity Server](https://junglewise.ai/threats/technologies/identity-server). Vendors: [Wso2](https://junglewise.ai/threats/vendors/wso2).

## Quick answers

**Is CVE-2025-1397 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-1397 being exploited in the wild.

**How severe is CVE-2025-1397?** Medium severity, with a CVSS score of 4.8, published 3 November 2026.

**Which products and versions are affected?** WSO2 Identity Server.

**Is there a fix for CVE-2025-1397?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2025-1397 attacked?** It is attacked over the network.

**Am I affected by CVE-2025-1397?** Check whether you run Wso2 Identity Server. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability exists in JWT Bearer and SAML2 Bearer grant type implementations, which do not validate the enabled/disabled status of the Identity Provider before token issuance. An attacker with knowledge of a disabled IDP's configuration can request access tokens that should not be issued, bypassing authentication controls. This is an authentication bypass affecting token generation logic.

## Affected products

- WSO2 Identity Server

## Timeline

- 2026-11-03: disclosed

## References

- [https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4010/](https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4010/)

## Related threats

- [WSO2 Identity Server privilege escalation via client credentials grant type](https://junglewise.ai/threats/cve-2025-11229-the-system-fails-to-properly-enforce-scope-authorization-when-the)
- [WSO2 Identity Server privilege escalation via shared database](https://junglewise.ai/threats/cve-2026-4052-this-issue-only-impacts-deployments-where-wso2-identity-server-is)
- [WSO2 products sensitive information disclosure in Event Publisher logs](https://junglewise.ai/threats/cve-2026-18800-when-an-event-publisher-output-adapter-is-configured-with)
- [WSO2 Identity Server content-type validation bypass](https://junglewise.ai/threats/cve-2025-13647-the-affected-component-fails-to-enforce-expected-validation)
- [WSO2 account lock bypass in multi-store authentication](https://junglewise.ai/threats/cve-2024-5617-the-account-lock-feature-fails-to-correctly-enforce-account)