Skip to content
Fencer Vulns
medium 4.3

CVE-2025-6623 json

Stored Cross-Site Scripting via XML Input in Multiple WSO2 Products Allows UI Manipulation and Redirection

published 2026-10-19 20 d ago modified 2026-11-04 4 d ago also EUVD-2025-211115

cvss
4.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 18%
public exploits
0
none known

Summary

The carbon console accepts user-supplied XML input without sufficiently encoding potentially executable content, allowing for the injection of malicious scripts.

Successful exploitation allows a remote attacker to execute arbitrary JavaScript in the context of a victim's browser, leading to actions such as redirecting the user to a malicious website or modifying the web page's user interface. Session hijacking is not possible as sensitive session cookies are protected by the httpOnly flag.

Patch / fix

  • WSO2 WSO2 API Manager 3.2.0.433, 3.2.1.53, 4.1.0.215, 4.2.0.153, 4.3.0.66, 4.4.0.29, 4.5.0.11
  • WSO2 WSO2 Universal Gateway 4.5.0.11
  • WSO2 WSO2 Traffic Manager 4.5.0.11
  • WSO2 WSO2 API Control Plane 4.5.0.12
  • WSO2 WSO2 Carbon Event Publisher UI 5.2.26.19, 5.2.41.6, 5.2.57.7, 5.3.5.4, 5.3.11.4, 5.3.15.3, 5.3.20.1
  • WSO2 WSO2 Carbon Event Receiver UI 5.2.26.19, 5.2.41.6, 5.2.57.7, 5.3.5.4, 5.3.11.4, 5.3.15.3, 5.3.20.1

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
19 d ago

Exploit prediction

0.27% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected products

  • WSO2 WSO2 API Manager
  • WSO2 WSO2 Universal Gateway
  • WSO2 WSO2 Traffic Manager
  • WSO2 WSO2 API Control Plane
  • WSO2 WSO2 Carbon Event Publisher UI
  • WSO2 WSO2 Carbon Event Receiver UI

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Vulns 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.