# CVE-2025-11229: WSO2 Identity Server privilege escalation via client credentials grant type

Source: https://junglewise.ai/threats/cve-2025-11229-the-system-fails-to-properly-enforce-scope-authorization-when-the  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-04. Updated: 2026-11-04  
License: CC BY 4.0 with a link back

CVE-2025-11229 · Severity: high · CVSS 7.2 · Published 2026-11-04

WSO2 Identity Server is an enterprise identity and access management platform that controls authentication and authorization for applications and APIs. When a specific configuration option is enabled (non-default), the system grants unrestricted API access to applications, allowing them to perform administrative actions and access sensitive data without proper authorization, potentially leading to account takeover.

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

## Quick answers

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

**How severe is CVE-2025-11229?** High severity, with a CVSS score of 7.2, published 4 November 2026.

**Which products and versions are affected?** Wso2 Identity Server 7.0.0, 7.1.0.

**Is there a fix for CVE-2025-11229?** Yes: fixed in WSO2 Identity Server 7.0.0 update level 125, 7.1.0 update level 32. Until then: Ensure the authorize_all_scopes configuration is set to false (the default) in the deployment.toml file. If it must remain enabled, also set authorize_internal_scopes = false to prevent internal and console scopes from being granted through the client credentials grant type. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2025-11229 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2025-11229?** Check whether you run Wso2 Identity Server at an affected version. 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.

## How to fix

- Fixed in WSO2 Identity Server 7.0.0 update level 125, 7.1.0 update level 32

Ensure the authorize_all_scopes configuration is set to false (the default) in the deployment.toml file. If it must remain enabled, also set authorize_internal_scopes = false to prevent internal and console scopes from being granted through the client credentials grant type.

## Technical details

The vulnerability exists in scope authorization enforcement when the authorize_all_scopes configuration is set to true (deviating from the default disabled state). Applications using the OAuth2 client credentials grant type can obtain all API scopes, including sensitive internal and console scopes, without explicit authorization. This allows privilege escalation and unauthorized administrative actions in non-default configurations.

## Affected products

- WSO2 Identity Server 7.0.0, 7.1.0

## Timeline

- 2026-01-26: disclosed

## References

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

## Related threats

- [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 Access token issuance without IDP status validation](https://junglewise.ai/threats/cve-2025-1397-when-utilizing-jwt-bearer-or-saml2-bearer-grant-types-the-system)
- [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)