WSO2 vulnerabilities
We track 48 vulnerabilities in WSO2 products across 60+ products. 48 are rated high or critical, and 2 have been exploited in real attacks. The most recent was published on November 4, 2026.
Latest WSO2 vulnerabilities
- 7.2 High severity
WSO2 Identity Server: Improper Privilege Management
The system fails to properly enforce scope authorization when the `authorize_all_scopes` configuration is enabled. This allows applications using the client credentials grant type to obtain all API scopes, including sensitive internal and console scopes, witho
- 9.8 Critical severity
WSO2 API Manager: Missing Authorization
This issue only impacts deployments where WSO2 Identity Server is configured as a Resident Key Manager with database sharing. In such environments, a self-registered user may gain access to the System REST APIs of WSO2 API Manager by obtaining a token from the
- 8.7 High severity
WSO2 API Manager: Improper Neutralization of Special Elements used in an SQL Command
The Admin REST API accepts user-supplied input without adequately sanitizing it, allowing it to be included in the structure of SQL statements. A user with administrator privileges can exploit this by influencing the structure of executed SQL statements, enabl
- 9.4 Critical severity
WSO2 API Manager: Improper Authorization
The System REST APIs do not correctly enforce access control mechanisms, allowing users with lower privilege roles to execute administrative actions that should be restricted. This weakness permits unauthorized operations on the affected product. Successful ex
- 8.8 High severity
Enterprise Integrator (BPS profile): Improper Neutralization of Special Elements used in an OS Command
The BPMN System REST APIs do not sufficiently validate input parameters, allowing authenticated users to submit crafted requests that can lead to the execution of arbitrary commands on the server. An authenticated user can leverage this vulnerability to execut
- 7.4 High severity
In deployments of WSO2 Identity Server configured with a case-insensitive user store and a…
In deployments of WSO2 Identity Server configured with a case-insensitive user store and a case-sensitive database for identity data, mismatches in username case handling can occur. This inconsistency results in OAuth token revocation operations failing to cor
- 8.3 High severity
WSO2 API Manager: Server-Side Request Forgery
Due to the improper implementation of access control rules, malicious actors could perform a Server Side Request Forgery (SSRF) attack on affected WSO2 Products. Exploiting this vulnerability allows a malicious actor to access both internal and external resour
- 7.4 High severity
The system fails to invalidate existing access tokens associated with sub-organization users…
The system fails to invalidate existing access tokens associated with sub-organization users during sensitive account management operations such as password reset, role change, or sub-organization disablement. This oversight allows previously issued tokens to
- 8.2 High severity
WSO2 Identity Server as Key Manager: Improper Preservation of Permissions
The SCIM endpoint does not sufficiently validate authorization for federated users when performing operations against the local user store. This occurs when a local and a federated user share the same username, allowing a federated user to perform actions inte
- 9.1 Critical severity
WSO2 Enterprise Integrator: Improper Neutralization of Special Elements used in an OS Command
The Management Console fails to properly validate input related to the configuration of JDBC user stores. This weakness allows an attacker to supply specially crafted input that can lead to the execution of arbitrary code on the affected server. Successful exp
- 7.0 High severity
WSO2 Integrator: MI for Visual Studio Code: Improper Neutralization of Special Elements used in an OS Command
The WSO2 Integrator MI VS Code extension fails to properly sanitize or validate user-supplied input when processing Micro Integrator projects opened from untrusted sources. This allows a crafted project to inject and execute arbitrary operating system commands
- 8.4 High severity
WSO2 Open Banking AM: Improper Neutralization of Special Elements used in an OS Command
The administrative operations within the Carbon Console do not adequately validate specific user-supplied input. This oversight allows a malicious actor with administrative privileges to inject and execute arbitrary code remotely. Successful exploitation enabl
- 7.5 High severity
WSO2 API Manager: Use of Insufficiently Random Values
The API Publisher component previously used a non-cryptographic pseudorandom number generator (PRNG) to create shared secrets for Webhook HMAC validation. This PRNG lacks sufficient entropy for security-sensitive operations, allowing a sophisticated attacker t
- 9.1 Critical severity
WSO2 API Manager: Unrestricted Upload of File with Dangerous Type
The System REST API accepts user-supplied file uploads without enforcing sufficient validation on the file type or destination, allowing files to be written to arbitrary server-accessible locations. Exploitation requires authenticated administrative access wit
- 8.7 High severity
WSO2 API Manager: Improper Restriction of Recursive Entity References in DTDs
The XML and schema validation functionalities within the SchemaValidator Mediator process XML input as part of validation flows. Under certain conditions, the XML parser allows the resolution of external entities when handling user-supplied XML content during
- 9.0 Critical severity
WSO2 API Manager: Improper Access Control
In multi-tenant deployments, the Publisher REST APIs fail to enforce tenant isolation correctly. This allows a user in one tenant, possessing sufficient privileges to invoke these APIs, to perform operations that impact other tenants. The vulnerability allows
- 10.0 Critical severity
WSO2 Multiple Products Path Traversal Exploited
The JWT authentication mechanism accepts tokens signed with algorithms other than those explicitly configured or supported. This allows an attacker to craft a JWT with an unsupported algorithm, which is then incorrectly validated, leading to unauthorized acces
- 9.8 Critical severity
WSO2 API Manager: Improper Privilege Management
Tokens issued to a low-privileged user are not sufficiently restricted, allowing them to be used to access product-level Admin REST APIs. Exploitation of this vulnerability allows a low-privileged user to invoke the Admin REST APIs of WSO2 products, potentiall
- 9.4 Critical severity
WSO2 Identity Server: Protection Mechanism Failure
The Conditional Authentication (Adaptive Authentication) script does not correctly enforce the completion of all required authentication steps when a specific multi-step pattern involving certain authenticators is configured. This allows an attacker to bypass
- 7.5 High severity
WSO2 Enterprise Integrator: Protection Mechanism Failure
The account locking mechanism fails to trigger when secondary user stores are inaccessible. The software does not maintain a consistent state for account locking if it cannot reach all configured user stores, allowing an attacker to repeatedly attempt authenti
- 8.6 High severity
WSO2 Universal Gateway: Improper Neutralization
The throttling event handling mechanism in multiple WSO2 products accepts user-supplied JSON payloads without sufficient validation of their structure and content. This allows an unauthenticated remote attacker to inject malicious JSON data that can lead to a
- 7.3 High severity
WSO2 Identity Server: Authentication Bypass Using an Alternate Path or Channel
In multi-tenanted deployments, the application consent management mechanism fails to correctly isolate consent scopes between tenants. Consent granted by a user for a specific SaaS application within one tenant can be incorrectly applied to SaaS applications w
- 10.0 Critical severity
WSO2 API Manager: Server-Side Request Forgery
The WSO2 API Manager's message flow component, when processing WS-Addressing headers, does not sufficiently validate or restrict user-controlled input within these headers. This omission allows an attacker to manipulate WS-Addressing headers to specify arbitra
- 7.2 High severity
WSO2 Identity Server: Improper Access Control
Due to not validating the organization context when executing adaptive authentication flows, the WSO2 Identity Server allows adaptive authentication logic to be triggered on unintended organizations. A malicious actor with privileges to configure adaptive auth
- 8.6 High severity
WSO2 Identity Server: Uncontrolled Resource Consumption
The Magic Link authentication flow accepts multiple invalid authentication requests without adequate rate limiting or resource control, leading to uncontrolled memory usage growth. This vulnerability can result in a denial-of-service condition, causing service
- 8.8 High severity
WSO2 API Control Plane: Improper Preservation of Permissions
The software fails to enforce role-based access controls for certain Gateway API invocations. Users with the 'Internal/Everyone' role can invoke these APIs, bypassing intended permission checks. This same vulnerability also affects Internal Service APIs, poten
- 7.5 High severity
WSO2 API Manager: Improper Neutralization of Special Elements in Output Used by a Downstream Component
In Webhook API invocations, the component accepts user-supplied input for HTTP request headers without sufficient validation or sanitization, allowing these headers to be injected into HTTP responses. By exploiting this vulnerability, a malicious actor can inj
- 7.3 High severity
WSO2 Identity Server: Incorrect Authorization
Due to a lack of user account state validation during authentication, locked user accounts can be successfully authenticated using Magic Link or Pass Key methods. This bypasses the intended security control that should prevent access to accounts that have been
- 7.5 High severity
WSO2 API Manager: Improper Restriction of XML External Entity Reference
The component accepts XML input through the publisher without disabling external entity resolution. This allows malicious actors to submit a crafted XML payload that exploits the unescaped external entity references. By leveraging this vulnerability, a malicio
- 9.1 Critical severity
WSO2 API Manager: Improper Restriction of XML External Entity Reference
The XML parsers within multiple WSO2 products accept user-supplied XML data without properly configuring to prevent the resolution of external entities. This omission allows malicious actors to craft XML payloads that exploit the parser's behavior, leading to
- 8.1 High severity
WSO2 API Manager: Authentication Bypass by Spoofing
When the "Silent Just-In-Time Provisioning" feature is enabled for a federated identity provider (IDP) there is a risk that a local user store user's information may be replaced during the account provisioning process in cases where federated users share the s
- 7.2 High severity
WSO2 API Manager: Unrestricted Upload of File with Dangerous Type
A malicious actor with administrative privileges can upload an arbitrary file to a user-controlled location within the deployment via a system REST API. Successful uploads may lead to remote code execution. By leveraging the vulnerability, a malicious actor ma
- 7.2 High severity
Identity Server: Improper Neutralization of Special Elements used in a Command
The Velocity template engine, utilized by the affected product, accepts and processes template syntax without sufficient sanitization or validation of user-controlled input. This allows an authenticated administrator to inject arbitrary template syntax. Succes
- 9.8 Critical severity
WSO2 API Manager: Missing Authentication for Critical Functionality
A missing authentication enforcement vulnerability exists in the mutual TLS (mTLS) implementation used by System REST APIs and SOAP services in multiple WSO2 products. Due to improper validation of client certificate–based authentication in certain default con
- 8.8 High severity
WSO2 Open Banking AM: Cross-Site Request Forgery
A Cross-Site Request Forgery (CSRF) vulnerability exists in multiple WSO2 products due to the use of the HTTP GET method for state-changing operations within admin services, specifically in the event processor of the Carbon console. Although the SameSite=Lax c
- 7.2 High severity
WSO2 Micro Integrator: Improper Control of Generation of Code
An arbitrary code execution vulnerability exists in multiple WSO2 products due to insufficient restrictions in the GraalJS and NashornJS Script Mediator engines. Authenticated users with elevated privileges can execute arbitrary code within the integration run
- 7.2 High severity
WSO2 API Manager: Unrestricted Upload of File with Dangerous Type
An arbitrary file upload vulnerability exists in multiple WSO2 products due to insufficient validation of uploaded content and destination in SOAP admin services. A malicious actor with administrative privileges can upload a specially crafted file to a user-co
- 9.1 Critical severity
WSO2 Enterprise Integrator: Improper Restriction of XML External Entity Reference
An XML External Entity (XXE) vulnerability exists in multiple WSO2 products due to improper configuration of the XML parser. The application parses user-supplied XML without applying sufficient restrictions, allowing resolution of external entities. A successf
- 7.2 High severity
WSO2 Identity Server: Unrestricted Upload of File with Dangerous Type
An arbitrary file upload vulnerability exists in multiple WSO2 products due to improper input validation in the CarbonAppUploader admin service endpoint. An authenticated attacker with appropriate privileges can upload a malicious file to a user-controlled loc
- 9.8 Critical severity
WSO2 API Manager: Missing Authentication for Critical Functionality
An improper privilege management vulnerability exists in WSO2 API Manager due to missing authentication and authorization checks in the keymanager-operations Dynamic Client Registration (DCR) endpoint. A malicious user can exploit this flaw to generate access