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

> Attackers can inject malicious scripts via the CTS close command field in the Web UI, potentially leading to session hijacking or code execution on the device.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Dec 2025
- **Updated:** 11 Dec 2025
- **Also known as:** GHSA-7vpr-g4pp-5q85

## What is CVE-2025-65231?

CVE-2025-65231 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 Dec 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

Barix Instreamer v04.06 and earlier is vulnerable to Cross Site Scripting (XSS) in the Web UI I/O & Serial configuration page, specifically the CTS close command user-input field which is stored and later rendered on the Status page.

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

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

It affects 1 product.


Products: Barix Instreamer Firmware.

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

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

## Is CVE-2025-65231 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65231 exists.

## Other vulnerabilities in n/a

- [CVE-2025-65230](https://insights.sbomify.com/CVE-2025-65230/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65231 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 Dec 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65231 exists.

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-65231/ (Markdown: https://insights.sbomify.com/CVE-2025-65231/index.md)
```

## Sources

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

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