# CVE-2023-34637: Cross-site scripting in n/a

> Authenticated attackers can execute arbitrary scripts via stored XSS in the dashboard title parameter of the IsarFlow portal.

- **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:** 5 Sep 2023
- **Updated:** 27 Sep 2024
- **Also known as:** GHSA-vx38-v98v-qh2f

## What is CVE-2023-34637?

CVE-2023-34637 is a medium-severity cross-site scripting vulnerability in n/a, published on 5 Sep 2023. 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 in IsarNet AG IsarFlow v5.23 allows authenticated attackers to execute arbitrary web scripts or HTML via injecting a crafted payload into the dashboard title parameter in the IsarFlow Portal.

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

## Which versions are affected by CVE-2023-34637?

It affects 1 product.


Products: Isarnet Isarflow.

## How do I fix CVE-2023-34637?

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

## Is CVE-2023-34637 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-34637 and fix it if it is affected.

What it is: CVE-2023-34637 is a medium-severity cross-site scripting vulnerability in n/a, published on 5 Sep 2023. Any signed-in user can exploit it over the network, 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-2023-34637 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-2023-34637/ (Markdown: https://insights.sbomify.com/CVE-2023-34637/index.md)
```

## Sources

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

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