CVE intelligence and bounded remediation
CVE-2025-5350 — Wso2 Api Control Plane security vulnerability
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.
- Severity
- Medium
- CVSS
- 5.9 (3.1)
- Published
- 2025-10-24
- CISA KEV
- Not currently listed
- Ecosystem
- javascript/npm
- Weaknesses
- CWE-79, CWE-918
Affected products
- wso2 / api_control_plane / 4.5.0
- wso2 / api_manager / 3.1.0
- wso2 / api_manager / 3.2.0
- wso2 / api_manager / 3.2.1
- wso2 / api_manager / 4.0.0
- wso2 / api_manager / 4.1.0
Matched remediation archetype
Server-side request forgery and unintended proxying
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Inventory server-side URL fetchers, webhooks, importers, previews, redirects, proxies, and protocol handlers reachable from untrusted input.
- Map egress paths to internal services, metadata endpoints, loopback, private address space, and privileged control planes.
- Review DNS resolution, redirect, proxy, credential-forwarding, and URL parsing behavior without requesting sensitive targets.
Remediate safely
- Replace arbitrary destinations with named integrations or a strict allowlist of schemes, hosts, ports, and paths.
- Resolve and validate every destination and redirect hop, then enforce egress policy independently of application checks.
- Remove ambient credentials and sensitive headers from fetchers; apply response size, time, and content limits.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.