This page lists publicly disclosed CVE vulnerabilities affecting wso2 api_manager (linked via NVD CPE). Each row includes severity scores, summaries, and publication dates to help identify and analyze security issues.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2025-8325 | 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, potentially exposing them in WSO2 APIM 3.x versions. A malicious actor with a valid user account on a vulnerable deployment can perform sensitive operations against the Gateway REST API regardless of their actual roles or privileges. This could | ed10eef1-636d-4fbe-9993-6890dfa878f8 | 6.3 | 0.17% | 2026-05-11 | 2026-05-27 |
| CVE-2025-8154 | 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 inject or overwrite arbitrary HTTP response headers. This can lead to various adverse effects, including the manipulation of browser caching, alteration of security-related headers, and the injection of sensitive information such as cookie va | ed10eef1-636d-4fbe-9993-6890dfa878f8 | 5.3 | 0.19% | 2026-05-11 | 2026-05-27 |
| CVE-2025-6024 | The authentication endpoint fails to encode user-supplied input before rendering it in the web page, allowing for script injection. An attacker can leverage this by injecting malicious scripts into the authentication endpoint. This can result in the user's browser being redirected to a malicious website, manipulation of the web page's user interface, or the retrieval of information from the browser. However, session hijacking is not possible due to the httpOnly flag protecting session-related co | ed10eef1-636d-4fbe-9993-6890dfa878f8 | 6.1 | 0.23% | 2026-04-16 | 2026-04-23 |
| CVE-2024-8010 | 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 malicious actor can read confidential files from the product's file system or access limited HTTP resources reachable via HTTP GET requests to the vulnerable product. | ed10eef1-636d-4fbe-9993-6890dfa878f8 | 3.5 | 0.27% | 2026-04-16 | 2026-04-23 |
| CVE-2024-4867 | The WSO2 API Manager developer portal accepts user-supplied input without enforcing expected validation constraints or proper output encoding. This deficiency allows a malicious actor to inject script content that is executed within the context of a user's browser. By leveraging this cross-site scripting vulnerability, a malicious actor can cause the browser to redirect to a malicious website, make changes to the UI of the web page, or retrieve information from the browser. However, session hij | ed10eef1-636d-4fbe-9993-6890dfa878f8 | 5.4 | 0.19% | 2026-04-16 | 2026-04-23 |
| CVE-2024-10242 | The authentication endpoint fails to adequately validate user-supplied input before reflecting it back in the response. This allows an attacker to inject malicious script payloads into the input parameters, which are then executed by the victim's browser. Successful exploitation can enable an attacker to redirect the user's browser to a malicious website, modify the UI of the web page, or retrieve information from the browser. However, the impact is limited as session-related sensitive cookies | ed10eef1-636d-4fbe-9993-6890dfa878f8 | 6.1 | 0.24% | 2026-04-16 | 2026-04-23 |
| CVE-2024-2374 | 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 the inclusion of external resources. By leveraging this vulnerability, an attacker can read confidential files from the file system and access limited HTTP resources reachable by the product. Additionally, the vulnerability can be exploite | ed10eef1-636d-4fbe-9993-6890dfa878f8 | 7.5 | 0.38% | 2026-04-16 | 2026-04-23 |
| CVE-2024-1524 | 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 same username as local users. There will be no impact on your deployment if any of the preconditions mentioned below are not met. Only when all the preconditions mentioned below are fulfilled could a malicious actor associate a targeted | ed10eef1-636d-4fbe-9993-6890dfa878f8 | 7.7 | 0.26% | 2026-02-24 | 2026-03-03 |
| CVE-2025-13590 | 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 may perform Remote Code Execution by uploading a specially crafted payload. | ed10eef1-636d-4fbe-9993-6890dfa878f8 | 9.1 | 0.68% | 2026-02-19 | 2026-02-20 |
| CVE-2025-9312 | 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 configurations, the affected components may permit unauthenticated requests even when mTLS is enabled. This condition occurs when relying on the default mTLS settings for System REST APIs or when the mTLS authenticator is enabled for SOAP serv | ed10eef1-636d-4fbe-9993-6890dfa878f8 | 9.8 | 0.21% | 2025-11-18 | 2025-12-08 |
| CVE-2025-6670 | 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 cookie attribute is used as a mitigation, it is ineffective in this context because it allows cookies to be sent with cross-origin top-level navigations using GET requests. A malicious actor can exploit this vulnerability by tricking an aut | ed10eef1-636d-4fbe-9993-6890dfa878f8 | 8.8 | 0.19% | 2025-11-18 | 2025-12-08 |
| CVE-2025-10853 | 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, leading to reflected XSS. Successful exploitation could result in UI manipulation, redirection to malicious websites, or data theft from the browser. However, session-related sensitive cookies are protected with the httpOnly flag, which mitigates | ed10eef1-636d-4fbe-9993-6890dfa878f8 | 5.2 | 0.17% | 2025-11-05 | 2025-11-13 |
| CVE-2025-5770 | A reflected cross-site scripting (XSS) vulnerability exists in the authentication endpoints of multiple WSO2 products due to a lack of output encoding. A malicious actor can inject arbitrary JavaScript payloads into the authentication endpoint, which are reflected back in the response, enabling browser-based attacks. Exploitation may result in redirection to malicious websites, UI manipulation, or unauthorized data access from the victim’s browser. However, session-related cookies are protected | ed10eef1-636d-4fbe-9993-6890dfa878f8 | 6.1 | 0.18% | 2025-11-05 | 2025-11-13 |
| CVE-2025-11093 | 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 runtime environment. By default, access to these scripting engines is limited to administrators in WSO2 Micro Integrator and WSO2 Enterprise Integrator, while in WSO2 API Manager, access extends to both administrators and API creators. This m | ed10eef1-636d-4fbe-9993-6890dfa878f8 | 8.4 | 0.42% | 2025-11-05 | 2026-01-09 |
| CVE-2025-10907 | 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-controlled location within the deployment. Successful exploitation may lead to remote code execution (RCE) on the server, depending on how the uploaded file is processed. By default, this vulnerability is only exploitable by users with admin | ed10eef1-636d-4fbe-9993-6890dfa878f8 | 8.4 | 0.52% | 2025-11-05 | 2025-12-04 |
| CVE-2025-10713 | 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 successful attack could enable a remote, unauthenticated attacker to read sensitive files from the server's filesystem or perform denial-of-service (DoS) attacks that render affected services unavailable. | ed10eef1-636d-4fbe-9993-6890dfa878f8 | 6.5 | 0.37% | 2025-11-05 | 2025-12-04 |
| CVE-2025-3125 | 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 location on the server, potentially leading to remote code execution (RCE). This functionality is restricted by default to admin users; therefore, successful exploitation requires valid credentials with administrative permissions. | ed10eef1-636d-4fbe-9993-6890dfa878f8 | 6.7 | 0.74% | 2025-11-05 | 2025-12-04 |
| CVE-2025-5605 | 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 partial information disclosure. The known exposure from this issue is limited to memory statistics. While the vulnerability does not allow full account compromise, it still enables unauthorized access to internal system details. | ed10eef1-636d-4fbe-9993-6890dfa878f8 | 4.3 | 0.87% | 2025-10-24 | 2025-11-21 |
| CVE-2025-5350 | 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 forgery (SSRF). Additionally, the retrieved content was directly reflected in the HTTP response, enabling reflected cross-site scripting (XSS) in the admin user's browser context. By tricking an administrator into accessing a crafted link, | ed10eef1-636d-4fbe-9993-6890dfa878f8 | 5.9 | 0.53% | 2025-10-24 | 2025-11-21 |
| CVE-2025-9804 | 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, including accessing server-level information. This vulnerability affects only internal administrative interfaces. APIs exposed through the WSO2 API Manager's API Gateway remain unaffected. | ed10eef1-636d-4fbe-9993-6890dfa878f8 | 9.6 | 0.51% | 2025-10-16 | 2025-11-21 |