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

> An authenticated admin can inject JavaScript into Kiamo pages, allowing code execution in other users' browsers.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Apr 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-8jxf-cjx5-gp4f

## What is CVE-2025-70365?

CVE-2025-70365 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A stored cross-site scripting (XSS) vulnerability exists in Kiamo before 8.4 due to improper output encoding of user-supplied input in administrative interfaces. An authenticated administrative user can inject arbitrary JavaScript code that is executed in the browser of users viewing the affected pages. NOTE: the Supplier's position is that a fix for this had already been released for the 8.3.1 branch before the CVE Record was published.

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

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


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

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

## Is CVE-2025-70365 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-70365 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-70365 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-70365/ (Markdown: https://insights.sbomify.com/CVE-2025-70365/index.md)
```

## Sources

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

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