# CVE-2025-5350: SSRF and Reflected XSS Vulnerability in Deprecated Try-It Feature of Multiple WSO2 Products > Attackers can exploit SSRF and XSS in the deprecated Try-It feature to execute arbitrary JavaScript and access internal services via admin interaction. - **Severity:** Medium 5.9 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 24 Oct 2025 - **Updated:** 24 Oct 2025 - **Also known as:** GHSA-h8cr-hjjr-3c8v ## What is CVE-2025-5350? CVE-2025-5350 is a medium-severity server-side request forgery vulnerability in Wso2 Api Manager, published on 24 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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. Weakness: CWE-918 (Server-Side Request Forgery), CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2025-5350? It affects 9 products. Products: Wso2 Api Control Plane, Wso2 Api Manager, Wso2 Enterprise Integrator, Wso2 Identity Server, Wso2 Identity Server as Key Manager, Wso2 Open Banking Am, Wso2 Open Banking Iam, Wso2 Traffic Manager, Wso2 Universal Gateway. ## How do I fix CVE-2025-5350? No fix has been published for CVE-2025-5350 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-5350 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5350 exists. Public exploit code: - WSO2 - Server Side Request Forgery (nuclei): http/cves/2025/CVE-2025-5350.yaml ## Other vulnerabilities in Wso2 Api Manager - [CVE-2026-5430](https://insights.sbomify.com/CVE-2026-5430/): WSO2 Multiple Products Path Traversal Vulnerability (critical 10.0, exploited in the wild) - [CVE-2026-1728](https://insights.sbomify.com/CVE-2026-1728/): Privilege Escalation via System REST APIs in Multiple WSO2 Products Permits Admin Account Takeover (critical 9.8) - [CVE-2025-9312](https://insights.sbomify.com/CVE-2025-9312/): Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products (critical 9.8) - [CVE-2025-10611](https://insights.sbomify.com/CVE-2025-10611/): Potential Broken Access Control in Multiple WSO2 Products via System REST APIs (critical 9.8) - [CVE-2025-9152](https://insights.sbomify.com/CVE-2025-9152/): Improper Privilege Management in Multiple WSO2 API Manager via keymanager-operations DCR Endpoint (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-5350 and fix it if it is affected. What it is: CVE-2025-5350 is a medium-severity server-side request forgery vulnerability in Wso2 Api Manager, published on 24 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5350 exists. Affected product: Wso2 Api Manager. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-5350/ (Markdown: https://insights.sbomify.com/CVE-2025-5350/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-5350 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-5350 - OSV: https://osv.dev/vulnerability/CVE-2025-5350 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-5350/ Summaries are generated and may contain mistakes; the official description above is the record.