CVE-2025-10611 json
Potential Broken Access Control in Multiple WSO2 Products via System REST APIs
published last yr. modified 4mo ago also EUVD-2025-34753
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- WSO2 WSO2 API Manager 2.1.0.42, 2.2.0.61, 2.5.0.87, 2.6.0.148, 3.0.0.178, 3.1.0.345, 3.2.0.446, 3.2.1.66, 4.0.0.366, 4.1.0.228, 4.2.0.169, 4.3.0.81, 4.4.0.45, 4.5.0.28
- WSO2 WSO2 API Control Plane 4.5.0.29
- WSO2 WSO2 Open Banking AM 1.4.0.141, 1.5.0.142, 2.0.0.394
- WSO2 WSO2 Open Banking IAM 2.0.0.414
- WSO2 WSO2 Identity Server 5.3.0.39, 5.5.0.54, 5.6.0.62, 5.7.0.128, 5.8.0.112, 5.9.0.171, 5.10.0.375, 5.11.0.419, 6.0.0.248, 6.1.0.248, 7.0.0.124, 7.1.0.31
- WSO2 WSO2 Identity Server as Key Manager 5.3.0.44, 5.5.0.55, 5.6.0.77, 5.7.0.127, 5.9.0.178, 5.10.0.365
- WSO2 WSO2 Open Banking KM 1.4.0.135, 1.5.0.125
- WSO2 WSO2 Universal Gateway 4.5.0.27
- WSO2 WSO2 Traffic Manager 4.5.0.27
- WSO2 org.wso2.carbon.identity.auth.rest:org.wso2.carbon.identity.auth.service 1.1.1.7, 1.1.16.6, 1.1.18.7, 1.1.20.9, 1.1.26.11, 1.3.6.11, 1.4.0.21, 1.4.25.27, 1.4.52.6, 1.6.1.12, 1.7.1.7, 1.8.11.8, 1.8.41.4, 1.8.48, 1.9.4.9, 1.9.18.7, 1.9.46
- WSO2 org.wso2.carbon.identity.auth.rest:org.wso2.carbon.identity.auth.valve 1.1.1.7, 1.1.16.6, 1.1.18.7, 1.1.20.9, 1.1.26.11, 1.3.6.11, 1.4.0.21, 1.4.25.27, 1.4.52.6, 1.6.1.12, 1.7.1.7, 1.8.11.8, 1.8.41.4, 1.8.48, 1.9.4.9, 1.9.18.7, 1.9.46
Is CVE-2025-10611 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.82% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- WSO2 WSO2 API Manager
- WSO2 WSO2 API Control Plane
- WSO2 WSO2 Open Banking AM
- WSO2 WSO2 Open Banking IAM
- WSO2 WSO2 Identity Server
- WSO2 WSO2 Identity Server as Key Manager
- WSO2 WSO2 Open Banking KM
- WSO2 WSO2 Universal Gateway
- WSO2 WSO2 Traffic Manager
- WSO2 org.wso2.carbon.identity.auth.rest:org.wso2.carbon.identity.auth.service
- WSO2 org.wso2.carbon.identity.auth.rest:org.wso2.carbon.identity.auth.valve
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
Sources
- CVE List CVE-2025-10611
- NVD CVE-2025-10611
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.