WSO2 Identity Server Try-It Feature server-side request forgery

Summaryinfo

A vulnerability classified as critical has been found in WSO2 Identity Server, Enterprise Integrator, API Manager, Universal Gateway, Traffic Manager, API Control Plane, Open Banking AM, Open Banking IAM, Identity Server as Key Manager and org.wso2.carbon:org.wso2.carbon.ui. Affected by this vulnerability is an unknown functionality of the component Try-It Feature. Performing a manipulation results in server-side request forgery. This vulnerability is cataloged as CVE-2025-5350. The attack must originate from the local network. There is no exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in WSO2 Identity Server, Enterprise Integrator, API Manager, Universal Gateway, Traffic Manager, API Control Plane, Open Banking AM, Open Banking IAM, Identity Server as Key Manager and org.wso2.carbon:org.wso2.carbon.ui. This affects some unknown processing of the component Try-It Feature. The manipulation with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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, an attacker could force the server to fetch malicious content and reflect it into the admin’s browser, leading to arbitrary JavaScript execution for UI manipulation or data exfiltration. While session cookies are protected with the HttpOnly flag, the XSS still poses a significant security risk. Furthermore, SSRF can be used by a privileged user to query internal services, potentially aiding in internal network enumeration if the target endpoints are reachable from the affected product.

The advisory is shared at security.docs.wso2.com. This vulnerability is uniquely identified as CVE-2025-5350 since 05/30/2025. The exploitability is told to be easy. Access to the local network is required for this attack to succeed. Additional levels of successful authentication are needed for exploitation. Neither technical details nor an exploit are publicly available.

Upgrading eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Banking Software

Vendor

• WSO2

Name

• API Control Plane
• API Manager
• Enterprise Integrator
• Identity Server
• Identity Server as Key Manager
• Open Banking AM
• Open Banking IAM
• org.wso2.carbon:org.wso2.carbon.ui
• Traffic Manager
• Universal Gateway

License

• commercial

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion