Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By WSO2

  2. · 16 months later

    Published

  3. · 1 day later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-6623, by who scored it
Scored byCVSSScoreVector
WSO2CNA (assigner)3.1Medium4.3CVSS:3.1/AV:A/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
NVDNVD · Awaiting Analysis3.1Medium4.3CVSS:3.1/AV:A/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N
EPSS (exploitation in 30 days)
0.27% · top 81% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.3.

Affected products

  • WSO2 · WSO2 API Manager

    • unknown < 3.2.0
    • affected 3.2.0 – < 3.2.0.433
    • affected 3.2.1 – < 3.2.1.53
    • affected 4.1.0 – < 4.1.0.215
    • affected 4.2.0 – < 4.2.0.153
    • affected 4.3.0 – < 4.3.0.66
    • affected 4.4.0 – < 4.4.0.29
    • affected 4.5.0 – < 4.5.0.11
  • WSO2 · WSO2 Universal Gateway

    • unknown < 4.5.0
    • affected 4.5.0 – < 4.5.0.11
  • WSO2 · WSO2 Traffic Manager

    • unknown < 4.5.0
    • affected 4.5.0 – < 4.5.0.11
  • WSO2 · WSO2 API Control Plane

    • unknown < 4.5.0
    • affected 4.5.0 – < 4.5.0.12
  • WSO2 · WSO2 Carbon Event Publisher UI

    • affected 5.2.26 – < 5.2.26.19
    • affected 5.2.41 – < 5.2.41.6
    • affected 5.2.57 – < 5.2.57.7
    • affected 5.3.5 – < 5.3.5.4
    • affected 5.3.11 – < 5.3.11.4
    • affected 5.3.15 – < 5.3.15.3
    • affected 5.3.20 – < 5.3.20.1
  • WSO2 · WSO2 Carbon Event Receiver UI

    • affected 5.2.26 – < 5.2.26.19
    • affected 5.2.41 – < 5.2.41.6
    • affected 5.2.57 – < 5.2.57.7
    • affected 5.3.5 – < 5.3.5.4
    • affected 5.3.11 – < 5.3.11.4
    • affected 5.3.15 – < 5.3.15.3
    • affected 5.3.20 – < 5.3.20.1

What to do

Solution: Follow the instructions given on https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4316/#solution

References

References2

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-6623 badge
[![CVE-2025-6623](https://cveledger.app/badge/CVE-2025-6623.svg)](https://cveledger.app/cve/CVE-2025-6623)

Record last updated .