`CVE-2025-5350`

Affected software	7 products, listed below
Severity	5.9 Medium CVSS 3.1 2 scores
Weakness	Cross-site scripting (CWE-79)
Published	24 Oct 2025
Updated	13 Nov 2026

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.

CWE-918 · Server-side request forgery

Exploitation status

Working exploit published

A reviewed exploit catalogue lists ready-to-run exploit code for this CVE.

CISA KEV not listed
VulnCheck KEV not listed
CISA Vulnrichment exploitation: none
Indexed PoC 1 indexed Published artifacts you can open, in Nuclei.
EPSS 0.62% chance in 30 days

Index	Artifact	Stars	First seen
Nuclei	WSO2 - Server Side Request Forgery

Index

Artifact

Stars

First seen

Nuclei

WSO2 - Server Side Request Forgery

Waratek protection

Rule in development

Waratek is working on a rule for this CVE. No rule is available yet, and it isn't certain the rule will work.

Current target: Q2 2027 (may change)

Protection none
Action in development patch rule; current target Q2 2027, may change
Review human Researcher
Record active

Decided by	A researcher's recorded decision for this specific CVE
Finding	A researcher set this CVE's status to Rule in development, naming the ARMR SSRF rule (in development).

Decided by

A researcher's recorded decision for this specific CVE

Finding

A researcher set this CVE's status to Rule in development, naming the ARMR SSRF rule (in development).

Waratek research note

written 2026-11-13

Written by a Waratek engineer who reviewed this CVE. Their decision sets the status above, ahead of every automated rule except a withdrawal.

Comments

Rule Name: SSRF rule (in development)

SSRF in the deprecated WSO2 Try-It proxy (WSRequestXSSproxy_ajaxprocessor.jsp): it fetches the Base64-encoded address in the uri request parameter and reflects the response. An SSRF rule in development is meant to block an outbound request to an address taken from request parameters. Nothing blocks this CVE until that rule ships.

CVSS

5.9 MEDIUM v3.1 CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L 2 metrics

We show the highest score from the newest CVSS version. Scores from different versions can't be compared, and the first score listed is sometimes a 0.0 placeholder.

Version Score Band Vector Assigner Type

CVSS 3.1 5.9 MEDIUM CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L WSO2 Secondary published

CVSS 3.1 4.8 MEDIUM CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N NVD Primary

Version	Score	Band	Vector	Assigner	Type
CVSS 3.1	5.9	MEDIUM	`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L`	WSO2	Secondary	published
CVSS 3.1	4.8	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`	NVD	Primary

Affected software and releases

Products and versions

9 products, 22 version entries

Source	Vendor	Product	Scheme	Affected versions
nvd	wso2	api control plane	generic	4.5.0
nvd	wso2	api manager	generic	3.1.0 · 3.2.0 · 3.2.1 · 4.0.0 · 4.1.0 · 4.2.0 · 4.3.0 · 4.4.0 · 4.5.0
nvd	wso2	enterprise integrator	generic	6.6.0
nvd	wso2	identity server	generic	5.10.0 · 5.11.0 · 6.0.0 · 6.1.0 · 7.0.0 · 7.1.0
nvd	wso2	identity server as key manager	generic	5.10.0
nvd	wso2	open banking am	generic	2.0.0
nvd	wso2	open banking iam	generic	2.0.0
nvd	wso2	traffic manager	generic	4.5.0
nvd	wso2	universal gateway	generic	4.5.0

Source

Vendor

Product

Scheme

Affected versions

nvd

wso2

api control plane

generic

4.5.0

nvd

wso2

api manager

generic

3.1.0 · 3.2.0 · 3.2.1 · 4.0.0 · 4.1.0 · 4.2.0 · 4.3.0 · 4.4.0 · 4.5.0

nvd

wso2

enterprise integrator

generic

6.6.0

nvd

wso2

identity server

generic

5.10.0 · 5.11.0 · 6.0.0 · 6.1.0 · 7.0.0 · 7.1.0

nvd

wso2

identity server as key manager

generic

5.10.0

nvd

wso2

open banking am

generic

2.0.0

nvd

wso2

open banking iam

generic

2.0.0

nvd

wso2

traffic manager

generic

4.5.0

nvd

wso2

universal gateway

generic

4.5.0

References

URL	Tags
https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2025/WSO2-2025-4124/	Vendor Advisory

URL

Timeline

Published	2025-10-24	By the CVE Program.
NVD record modified	2026-06-17	NVD's own last-modified date for this record.
Classification created	2026-11-13	First commit adding this CVE's research note.
Last VRT activity	2026-11-13	Most recent commit touching this CVE's classification, patch or rule file.

Published

2025-10-24

By the CVE Program.

NVD record modified

2026-06-17

NVD's own last-modified date for this record.

Classification created

2026-11-13

First commit adding this CVE's research note.

Last VRT activity

2026-11-13

Most recent commit touching this CVE's classification, patch or rule file.

How VRT decided (4 of 24 rules ran)

4 of 24 rules ran. The rest didn't run because an earlier rule had already settled the CVE.

# Rule Outcome Status Detail

identity: Does this identifier describe a vulnerability at all? the first rule that matches decides

1 rejected no match CVE Program withdrawal of this identifier

scope: Is it a vulnerability Waratek protects? the first rule that matches decides

2 armr-patch-file no match An ARMR patch file on disk for this CVE

3 armr-secure-rule-file no match An ARMR security-rule template on disk for this CVE

4 manual-classification decided it matched Rule in development A researcher set this CVE's status to Rule in development, naming the ARMR SSRF rule (in development).

5 manual classification not reached Manual classification of this CVE in the legacy dataset

6 non-java-upstream not reached A root cause in non-Java code: an OS kernel, a C library, or a bundled runtime

7 oracle-component not reached The defect being in a component of a tracked product the agent does not reach: JavaFX, the Java SE installer, the JInitiator browser plug-in, the native WebLogic proxy plug-in, or a native part of Oracle Application Server or Collaboration Suite (HTTP Server, Web Cache, Internet Directory, mail and calendar servers). Oracle gives these no CPE of their own and names them only in the description.

8 java-client-side not reached Oracle's own risk-matrix note saying the CVE is reached only through untrusted code in the Java sandbox (applets, Web Start) or only through a client installation of Java, so a server running its own trusted code is not exposed

9 osv-maven not reached An OSV.dev record of this CVE affecting a package published to Maven Central. When every such package is one business applications do not use (Minecraft mods and launchers, Fastjson) and no tracked product is named by CPE, it settles the CVE as Outside Waratek scope instead

10 cna-maven-package not reached An affected Maven artifact named by the CNA itself

11 known-cpe-product not reached An NVD CPE naming a product ARMR tracks

12 cna-cpe-product not reached A CPE the CNA published naming a tracked product. Oracle publishes these on advisory day, months before NVD.

13 oracle-advisory-family not reached A tracked product family named in Oracle's own risk matrix. CPE cannot carry a suite name, only a module.

14 cna-named-product not reached A tracked product named in words by the CVE's own CNA, on a record with no CPE yet. Apache and Eclipse publish these on advisory day, before NVD adds CPE data.

15 non-deployable-product not reached The only affected product being a sealed appliance image, where Java runs but no -javaagent can be attached

16 unmatched-product not reached No tracked product matched above, and none present at all

disposition: What do we do about one that is? every rule runs

17 patch-hint not reached A reference pointing at the upstream fix: a commit, a PR, a Red Hat bug

18 open-source-maven not reached The affected package being open source on Maven, so the fix can be read

19 poc-derivable not reached An indexed exploit clearing the evidence bar to reverse-engineer, where there is no source to read

20 no-exploit not reached Nothing to build a rule from yet: no published exploit, no CISA record of exploitation and no source-level change to read

21 secure-rule-match not reached A vulnerability class already blocked by an ARMR security rule

22 exploited-no-fix-or-poc not reached Somebody exploiting this CVE (a CISA or VulnCheck KEV listing, or a CISA verdict of active exploitation), with no fix, source code or PoC to build a rule from

23 below-action-threshold not reached Medium or Low severity, no CISA or VulnCheck KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory

24 no-exploit-published not reached Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all

NVD ↗ · CVE.org ↗