# CVE-2025-27828: Cross-site scripting in n/a

> An unauthenticated attacker can execute arbitrary scripts via reflected XSS in the legacy chat component, requiring user interaction to compromise confidentiality and integrity.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Jun 2025
- **Updated:** 24 Jun 2025
- **Also known as:** GHSA-56h7-86m5-vpw2

## What is CVE-2025-27828?

CVE-2025-27828 is a high-severity cross-site scripting vulnerability in n/a, published on 24 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the legacy chat component of Mitel MiContact Center Business through 10.0.0.4, 10.1.0.0 through 10.1.0.5, and 10.2.0.0 through 10.2.0.4 could allow an unauthenticated attacker to conduct a reflected cross-site scripting (XSS) attack due to insufficient input validation. A successful exploit requires user interaction and could allow an attacker to execute arbitrary scripts with a limited impact on the confidentiality and the integrity.

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

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


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

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

## Is CVE-2025-27828 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27828 is a high-severity cross-site scripting vulnerability in n/a, published on 24 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-27828 in the wild and no public exploit code.

Affected product: n/a. 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-27828/ (Markdown: https://insights.sbomify.com/CVE-2025-27828/index.md)
```

## Sources

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

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