Skip to content
Fencer Intel
medium 5.9

CVE-2025-5350 json

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

published last yr. modified 4mo ago also EUVD-2025-35829

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 49%
public exploits
0
none known, plus a Nuclei check

Summary

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.

Patch / fix

  • WSO2 WSO2 Identity Server 5.10.0.359, 5.11.0.415, 6.0.0.246, 6.1.0.245, 7.0.0.120, 7.1.0.27
  • WSO2 WSO2 Enterprise Integrator 6.6.0.218
  • WSO2 WSO2 API Manager 3.1.0.332, 3.2.0.428, 3.2.1.47, 4.0.0.369, 4.1.0.209, 4.2.0.147, 4.3.0.60, 4.4.0.23, 4.5.0.7
  • WSO2 WSO2 Universal Gateway 4.5.0.7
  • WSO2 WSO2 Traffic Manager 4.5.0.7
  • WSO2 WSO2 API Control Plane 4.5.0.7
  • WSO2 WSO2 Open Banking AM 2.0.0.380
  • WSO2 WSO2 Open Banking IAM 2.0.0.401
  • WSO2 WSO2 Identity Server as Key Manager 5.10.0.352
  • WSO2 org.wso2.carbon:org.wso2.carbon.ui 4.5.3.41, 4.6.0.1087, 4.6.1.151, 4.6.2.672, 4.6.3.30, 4.6.4.7, 4.7.1.70, 4.8.1.32, 4.9.0.101, 4.9.26.19, 4.9.27.3, 4.9.28.1, 4.9.29, 4.10.9.69, 4.10.42.11, 4.10.93

Is CVE-2025-5350 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.62% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L
NVD 3.1 4.8 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

Affected products

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

Classification

Weakness
  • CWE-918 Server-Side Request Forgery
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.