# CVE-2025-10853: Reflected Cross-Site Scripting (XSS) in Management Console of Multiple WSO2 Products Due to Improper Output Encoding

> Attackers can inject JavaScript into WSO2 management consoles via reflected XSS, enabling UI manipulation and data theft, though session hijacking is mitigated.

- **Severity:** Medium 5.2 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Nov 2025
- **Updated:** 5 Nov 2025
- **Also known as:** GHSA-4x6x-rggp-ff9q

## What is CVE-2025-10853?

CVE-2025-10853 is a medium-severity cross-site scripting vulnerability in Wso2 Api Manager, published on 5 Nov 2025. 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

A reflected cross-site scripting (XSS) vulnerability exists in the management console of multiple WSO2 products due to improper output encoding. By tampering with specific parameters, a malicious actor can inject arbitrary JavaScript into the response, leading to reflected XSS.

Successful exploitation could result in UI manipulation, redirection to malicious websites, or data theft from the browser. However, session-related sensitive cookies are protected with the httpOnly flag, which mitigates the risk of session hijacking.

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

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

It affects 9 products.


Products: Wso2 Api Control Plane, Wso2 Api Manager, Wso2 Enterprise Integrator, Wso2 Identity Server, Wso2 Identity Server as Key Manager, Wso2 Open Banking Am, Wso2 Open Banking Iam, Wso2 Traffic Manager, Wso2 Universal Gateway.

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

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

## Is CVE-2025-10853 being exploited?

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

## Other vulnerabilities in Wso2 Api Manager

- [CVE-2026-5430](https://insights.sbomify.com/CVE-2026-5430/): WSO2 Multiple Products Path Traversal Vulnerability (critical 10.0, exploited in the wild)
- [CVE-2026-1728](https://insights.sbomify.com/CVE-2026-1728/): Privilege Escalation via System REST APIs in Multiple WSO2 Products Permits Admin Account Takeover (critical 9.8)
- [CVE-2025-9312](https://insights.sbomify.com/CVE-2025-9312/): Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products (critical 9.8)
- [CVE-2025-10611](https://insights.sbomify.com/CVE-2025-10611/): Potential Broken Access Control in Multiple WSO2 Products via System REST APIs (critical 9.8)
- [CVE-2025-9152](https://insights.sbomify.com/CVE-2025-9152/): Improper Privilege Management in Multiple WSO2 API Manager via keymanager-operations DCR Endpoint (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10853 is a medium-severity cross-site scripting vulnerability in Wso2 Api Manager, published on 5 Nov 2025. 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-10853 in the wild and no public exploit code.

Affected product: Wso2 Api Manager. 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-10853/ (Markdown: https://insights.sbomify.com/CVE-2025-10853/index.md)
```

## Sources

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

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