Skip to content
OpenAdvisories

Product · WSO2

WSO2 Identity Server as Key Manager

54 known vulnerabilities.

WSO2 Identity Server as Key Manager at a glance

Last 12 months
31
Critical · all time
5
Exploited · all time
0
Public exploit · all time
0
New vulnerabilities per month · last 12 months
0 5 10 December 2025: 0 vulnerabilities Dec 2025 January 2026: 0 vulnerabilities February 2026: 0 vulnerabilities March 2026: 0 vulnerabilities Mar April 2026: 1 vulnerability May 2026: 1 vulnerability June 2026: 0 vulnerabilities Jun July 2026: 2 vulnerabilities August 2026: 6 vulnerabilities, 1 critical September 2026: 2 vulnerabilities Sep October 2026: 10 vulnerabilities, 1 critical November 2026: 7 vulnerabilities, 1 critical
Show as table
MonthVulnerabilitiesCritical
Nov 202671
Oct 2026101
Sep 202620
Aug 202661
Jul 202620
Jun 202600
May 202610
Apr 202610
Mar 202600
Feb 202600
Jan 202600
Dec 202500
Nov 202571
Oct 202541
Sep 202550
Aug 202500
Jul 202500
Jun 202550
May 202530
Apr 202500
Mar 202500
Feb 202500
Jan 202500
Dec 202400

54 results · Feed

  • Medium 4.8

    Improper IDP Status Validation via JWT Bearer or SAML2 Bearer Grants in Multiple WSO2 Products Allows Access Token Issuance for Disabled Identity Providers

    When utilizing JWT Bearer or SAML2 Bearer grant types, the system fails to validate the status of the Identity Provider (IDP) before issuing access tokens. This oversight permits tokens to be generated even when the associated IDP has been disabled. A malicio…

  • Medium 4.3

    Content Spoofing via Error Handling in Multiple WSO2 Products Enables Social Engineering Attacks

    The error handling implementation fails to properly sanitize or validate user-supplied input within URL parameters under specific conditions. This allows end-users to manipulate the error messages that are displayed by the application. By exploiting this vuln…

  • Medium 4.9

    Improper Token Renewal in Refresh Token Grant in Multiple WSO2 Products Allows Unauthorized Access to Blocked Accounts

    The refresh token grant type in WSO2 products fails to re-validate account status before issuing new access tokens. This weakness allows an attacker to obtain valid access tokens for user accounts even after they have been blocked by the user store, bypassing…

  • Medium 5.4

    Open Redirection via Unsanitized User Input in Multiple WSO2 Products Allows Phishing Attacks

    The affected components accept user-supplied input for constructing redirection URLs without enforcing expected validation constraints. This allows an attacker to provide a crafted URL that can redirect users to an arbitrary external domain. By leveraging thi…

  • Medium 4.4

    Information Disclosure via Event Publisher Logging in Multiple WSO2 Products Allows Retrieval of Sensitive Data

    When an Event Publisher output adapter is configured with properties that are irrelevant to its function, the affected products log these irrelevant properties. This can inadvertently include sensitive user credentials or other confidential information depend…

  • Medium 5.8

    Information Disclosure in Multiple WSO2 Products Allows Exposure of Certificate File Paths

    The affected component fails to enforce expected validation constraints on the `content-type` header when processing certain requests. This allows an attacker to submit a crafted request with a manipulated `content-type` header. Successful exploitation can le…

  • Critical 9.4

    Broken Access Control via System REST APIs in Multiple WSO2 Products Allows Unauthorized Administrative Actions

    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 e…

  • Low 3.1

    Improper Token Revocation via OAuth2 Scope Enforcement in Multiple WSO2 Products [Disrupted Authentication Flows]

    When the `allowed_scopes` configuration is enabled, the OAuth2 token introspection mechanism does not immediately invalidate a token in the cache after a revocation request. This results in a scenario where an access token that was introspected immediately be…

  • High 8.3

    Server Side Request Forgery in Multiple WSO2 Products Allows Access to Internal and External Resources

    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 resou…

  • Medium 4.0

    Sensitive Data Exposure via URL Parameters in Multiple WSO2 Products Allows Confidential Information Leakage

    The product failed to enforce validation constraints on user-supplied input in URL parameters, allowing sensitive data to be passed to flows where it was not intended to be processed. Although the product did not utilize this data, its acceptance could lead t…

  • Medium 5.8

    Username Enumeration via External User Stores in Multiple WSO2 Products Allows User Account Discovery

    When a WSO2 product is configured to use an external user store, the system fails to adequately obscure the existence or validity of usernames during authentication attempts. This oversight allows an attacker to repeatedly query the authentication mechanism w…

  • Medium 6.1

    Cross-Site Scripting via Authentication Endpoint in Multiple WSO2 Products Enables UI Manipulation and Redirection

    The Authentication Endpoint accepts user-supplied input without sufficient encoding, allowing for the injection of malicious JavaScript payloads. This vulnerability can be triggered by submitting crafted input to the Authentication Endpoint. Successful exploi…

  • Medium 4.8

    Password Brute Force via Password History Validation in Multiple WSO2 Products Allows User Account Discovery

    The RemoteUserStoreManagerService does not sufficiently validate password change attempts when the password history validation feature is enabled. This oversight allows an attacker to repeatedly attempt password guesses for a user account without being adequa…

  • Low 2.7

    Expression Language Injection via User Input in Multiple WSO2 Products Permits Arbitrary Operations

    The software accepts user-supplied data without sufficient validation, allowing for the injection of malicious Expression Language (EL) code. This can lead to the execution of arbitrary operations within the affected deployment. Exploitation of this vulnerabi…

  • Medium 6.5

    Improper Token Revocation via Session-Bound Token Flow in Multiple WSO2 Products Allows Unauthorized Access After Session Termination

    Tokens associated with user sessions are not revoked when the corresponding user session is terminated, unless another SSO request is initiated. This occurs when the session-bound token feature is enabled with token binding validation and the "Revoke token up…

  • High 8.2

    Arbitrary Operations via SCIM Endpoints in Multiple WSO2 Products Enables User Account Takeover

    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 int…

  • Critical 9.1

    Remote Code Execution via JDBC User Store Configuration in Multiple WSO2 Products Allows Arbitrary Code Execution

    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 ex…

  • Medium 5.3

    Username Enumeration via Self Registration Flow in Multiple WSO2 Products Allows User Account Discovery

    The self-registration flow accepts user-supplied input for usernames without adequately preventing the disclosure of username existence. When a user attempts to register with an existing username, the system responds with an error message that explicitly indi…

  • High 8.4

    Arbitrary Code Execution via Administrative Operations in Multiple WSO2 Products Allows Remote Code Execution

    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 enab…

  • Critical 9.4

    Account Takeover via Conditional Authentication Script Logic in Multiple WSO2 Products

    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…

  • Medium 5.4

    Cross-Site Request Forgery via Ajax Processor Endpoints in Multiple WSO2 Products Enables Unauthorized Actions

    The Ajax processor within the Carbon console fails to adequately protect state-changing operations from Cross-Site Request Forgery (CSRF) attacks. Specifically, it utilizes the HTTP GET method for these operations, and while the SameSite=Lax cookie attribute …

  • Low 3.7

    Username Enumeration via Login Interface in Multiple WSO2 Products Allows User Account Discovery

    When Multi-Attribute Login is enabled, the login interface fails to consistently mask the existence of user accounts. For valid users, the server resolves and displays their canonical username, while for non-existent users, it echoes the original input. This …

  • Medium 4.0

    Improper Input Validation via Signup Process in Multiple WSO2 Products Enables Content Manipulation and Data Exposure

    The user self-signup flow in multiple WSO2 products fails to adequately validate user-supplied input. This weakness allows arbitrary unvalidated data to be included within user claims, which are then used by downstream processes. Allowing unvalidated input in…

  • Medium 5.9

    Account Lockout Failure via Secondary User Store Inaccessibility in Multiple WSO2 Products Allows Brute Force Attacks

    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 authent…

  • Medium 4.9

    Authorization Code issued for Deleted User reuse in Multiple WSO2 Products Allows Unauthorized Access

    Unused authorization codes issued to deleted users are not being properly invalidated or removed from the system. This allows for the persistence of these codes, enabling them to be potentially reused. If an attacker possesses both the authorization code and …

  • Medium 6.1

    Reflected Cross-Site Scripting via URL Parameter in Multiple WSO2 Products Enables UI Modification

    The software accepts user-supplied input via a URL parameter without adequate output encoding before reflecting it back to the user's browser. This condition allows an attacker to inject malicious script content into pages served by the application. By levera…

  • Medium 4.8

    Role Overwriting via Silent JIT Provisioning in Multiple WSO2 Products Enables Privilege Escalation

    The silent Just-In-Time (JIT) provisioning feature in federated authentication implementations fails to properly segregate user roles during account creation when a federated user shares a username with a local user. This allows the provisioning process to ov…

  • Medium 5.3

    Username Enumeration via Email OTP Flow in Multiple WSO2 Products Allows User Account Discovery

    The check user account lock states feature within the email OTP flow fails to validate user input, allowing an attacker to infer the existence of registered user accounts. The discovery of valid usernames can increase the risk of brute-force and social engine…

  • High 7.5

    XML External Entity Injection in Multiple WSO2 Products Allows Arbitrary file read and Denial of Service

    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…

  • Critical 9.8

    Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products

    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 co…

  • High 8.8

    Cross-Site Request Forgery (CSRF) in Multiple WSO2 Products via HTTP GET in Admin Services

    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 …

  • Medium 5.2

    Reflected Cross-Site Scripting (XSS) in Management Console of Multiple WSO2 Products Due to Improper Output Encoding

    A reflected cross-site scripting (XSS) vulnerability exists in the management console of multiple WSO2 products due to improper output encoding. By tampering with specific parameters, a malicious actor can inject arbitrary JavaScript into the response, leadin…

  • High 8.4

    Arbitrary Code Execution with higher privileged users in Multiple WSO2 Products via Script Mediator Engines (GraalJS and NashornJS)

    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 ru…

  • High 8.4

    Authenticated Arbitrary File Upload in Multiple WSO2 Products via SOAP Admin Services Leading to Remote Code Execution

    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-c…

  • Medium 6.5

    XML External Entity (XXE) Vulnerability in Multiple WSO2 Products Due to Improper XML Parser Configuration

    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 success…

  • Medium 6.7

    Authenticated Arbitrary File Upload in Multiple WSO2 Products via CarbonAppUploader Admin Service Leading to Remote Code Execution

    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 lo…

  • Medium 4.3
    CVE-2025-5605 Scanner template

    Authentication Bypass via URI Manipulation in Multiple WSO2 Products' Management Console Leading to Partial Information Disclosure

    An authentication bypass vulnerability exists in the Management Console of multiple WSO2 products. A malicious actor with access to the console can manipulate the request URI to bypass authentication and access certain restricted resources, resulting in parti…

  • Medium 5.9
    CVE-2025-5350 Scanner template

    SSRF and Reflected XSS Vulnerability in Deprecated Try-It Feature of Multiple WSO2 Products

    SSRF and Reflected XSS Vulnerabilities exist in multiple WSO2 products within the deprecated Try-It feature, which was accessible only to administrative users. This feature accepted user-supplied URLs without proper validation, leading to server-side request …

  • High 8.9

    Improper Access Control in Multiple WSO2 Products via Internal SOAP Admin Services and System REST APIs

    An improper access control vulnerability exists in multiple WSO2 products due to insufficient permission enforcement in certain internal SOAP Admin Services and System REST APIs. A low-privileged user may exploit this flaw to perform unauthorized operations, …

  • Critical 9.8

    Potential Broken Access Control in Multiple WSO2 Products via System REST APIs

    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…