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

> Remote attackers can inject malicious scripts via XML input in WSO2 products, enabling UI manipulation and user redirection.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-34w7-4f3v-wc5q

## What is CVE-2025-6623?

CVE-2025-6623 is a medium-severity cross-site scripting vulnerability in WSO2 API Control Plane, published on 19 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-6623?


## How do I fix CVE-2025-6623?

No fix has been published for CVE-2025-6623 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-6623 being exploited?

There is no known exploitation of CVE-2025-6623 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6623 and fix it if it is affected.

What it is: CVE-2025-6623 is a medium-severity cross-site scripting vulnerability in WSO2 API Control Plane, published on 19 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-6623 in the wild and no public exploit code.

Affected product: WSO2 API Control Plane. 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-6623/ (Markdown: https://insights.sbomify.com/CVE-2025-6623/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-6623
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-6623
- OSV: https://osv.dev/vulnerability/CVE-2025-6623

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-6623/
Summaries are generated and may contain mistakes; the official description above is the record.