CyberSecBulletin
CVE-2025-10611NVD status: Analyzed

WSO2 API Manager: Incorrect Authorization

Published Updated By the CyberSecBulletin desk

CVE-2025-10611 is a critical-severity incorrect authorization vulnerability in WSO2 API Manager from WSO2, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 2.1.0.42, 2.2.0.61, 2.5.0.87 as the first without the flaw, so updating WSO2 API Manager to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.82% chance of exploitation within 30 days, higher than 58% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update WSO2 API Manager to 2.1.0.42 or 2.2.0.61 or 2.5.0.87 or 2.6.0.148, whichever matches your release line, or a later version.
  2. Update WSO2 API Control Plane to 4.5.0.29 or a later version.
  3. Update WSO2 Open Banking AM to 1.4.0.141 or 1.5.0.142 or 2.0.0.394, 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. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
WSO2WSO2 API Manager2.1.0 up to, but not including, 2.1.0.42; 2.2.0 up to, but not including, 2.2.0.61; 2.5.0 up to, but not including, 2.5.0.87; 2.6.0 up to, but not including, 2.6.0.148; 3.0.0 up to, but not including, 3.0.0.178; 3.1.0 up to, but not including, 3.1.0.345; 3.2.0 up to, but not including, 3.2.0.446; 3.2.1 up to, but not including, 3.2.1.66; and 6 more ranges2.1.0.42, 2.2.0.61, 2.5.0.87, 2.6.0.148, 3.0.0.178, 3.1.0.345
WSO2WSO2 API Control Plane4.5.0 up to, but not including, 4.5.0.294.5.0.29
WSO2WSO2 Open Banking AM1.4.0 up to, but not including, 1.4.0.141; 1.5.0 up to, but not including, 1.5.0.142; 2.0.0 up to, but not including, 2.0.0.3941.4.0.141, 1.5.0.142, 2.0.0.394
WSO2WSO2 Open Banking IAM2.0.0 up to, but not including, 2.0.0.4142.0.0.414
WSO2WSO2 Identity Server5.3.0 up to, but not including, 5.3.0.39; 5.5.0 up to, but not including, 5.5.0.54; 5.6.0 up to, but not including, 5.6.0.62; 5.7.0 up to, but not including, 5.7.0.128; 5.8.0 up to, but not including, 5.8.0.112; 5.9.0 up to, but not including, 5.9.0.171; 5.10.0 up to, but not including, 5.10.0.375; 5.11.0 up to, but not including, 5.11.0.419; and 4 more ranges5.3.0.39, 5.5.0.54, 5.6.0.62, 5.7.0.128, 5.8.0.112, 5.9.0.171
WSO2WSO2 Identity Server as Key Manager5.3.0 up to, but not including, 5.3.0.44; 5.5.0 up to, but not including, 5.5.0.55; 5.6.0 up to, but not including, 5.6.0.77; 5.7.0 up to, but not including, 5.7.0.127; 5.9.0 up to, but not including, 5.9.0.178; 5.10.0 up to, but not including, 5.10.0.3655.3.0.44, 5.5.0.55, 5.6.0.77, 5.7.0.127, 5.9.0.178, 5.10.0.365
WSO2WSO2 Open Banking KM1.4.0 up to, but not including, 1.4.0.135; 1.5.0 up to, but not including, 1.5.0.1251.4.0.135, 1.5.0.125
WSO2WSO2 Universal Gateway4.5.0 up to, but not including, 4.5.0.274.5.0.27
WSO2WSO2 Traffic Manager4.5.0 up to, but not including, 4.5.0.274.5.0.27
WSO2org.wso2.carbon.identity.auth.rest:org.wso2.carbon.identity.auth.service1.1.1 up to, but not including, 1.1.1.7; 1.1.16 up to, but not including, 1.1.16.6; 1.1.18 up to, but not including, 1.1.18.7; 1.1.20 up to, but not including, 1.1.20.9; 1.1.26 up to, but not including, 1.1.26.11; 1.3.6 up to, but not including, 1.3.6.11; 1.4.0 up to, but not including, 1.4.0.21; 1.4.25 up to, but not including, 1.4.25.27; and 8 more ranges1.1.1.7, 1.1.16.6, 1.1.18.7, 1.1.20.9, 1.1.26.11, 1.3.6.11
WSO2org.wso2.carbon.identity.auth.rest:org.wso2.carbon.identity.auth.valve1.1.1 up to, but not including, 1.1.1.7; 1.1.16 up to, but not including, 1.1.16.6; 1.1.18 up to, but not including, 1.1.18.7; 1.1.20 up to, but not including, 1.1.20.9; 1.1.26 up to, but not including, 1.1.26.11; 1.3.6 up to, but not including, 1.3.6.11; 1.4.0 up to, but not including, 1.4.0.21; 1.4.25 up to, but not including, 1.4.25.27; and 8 more ranges1.1.1.7, 1.1.16.6, 1.1.18.7, 1.1.20.9, 1.1.26.11, 1.3.6.11
WSO2API Control Plane4.5.0Not stated
WSO2API Manager2.1.0; 2.2.0; 2.5.0; 2.6.0; 3.0.0; 3.1.0; 3.2.0; 3.2.1; and 6 more rangesNot stated
WSO2Identity Server5.3.0; 5.5.0; 5.6.0; 5.7.0; 5.8.0; 5.9.0; 5.10.0; 5.11.0; and 4 more rangesNot stated
WSO2Identity Server As Key Manager5.3.0; 5.5.0; 5.6.0; 5.7.0; 5.9.0; 5.10.0Not stated
WSO2Open Banking Am1.4.0; 1.5.0; 2.0.0Not stated
WSO2Open Banking Iam2.0.0Not stated
WSO2Open Banking Km1.4.0; 1.5.0Not stated
WSO2Traffic Manager4.5.0Not stated
WSO2Universal Gateway4.5.0Not stated

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
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
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
HighThe component can be taken down completely.

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

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

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

The underlying weakness: Incorrect Authorization

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

How developers prevent this class of flaw

  • Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.

More Incorrect Authorization vulnerabilities (CWE-863)

Timeline

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

References

Other vulnerabilities in WSO2 API Manager

All WSO2 API Manager vulnerabilities

Recent Incorrect Authorization vulnerabilities

Spotted an error? Tell us.