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

> Attackers can inject malicious scripts into ontology fields to steal Protected Health Information from users of IMPatienT.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/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:** 17 Jan 2023
- **Updated:** 4 Apr 2025
- **Also known as:** GHSA-fqgh-j4x2-5297

## What is CVE-2023-23637?

CVE-2023-23637 is a high-severity cross-site scripting vulnerability in n/a, published on 17 Jan 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

IMPatienT before 1.5.2 allows stored XSS via onmouseover in certain text fields within a PATCH /modify_onto request to the ontology builder. This may allow attackers to steal Protected Health Information.

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

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

It affects 1 product.


Products: Unistra Impatient.

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

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

## Is CVE-2023-23637 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-23637 is a high-severity cross-site scripting vulnerability in n/a, published on 17 Jan 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-23637 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-23637/ (Markdown: https://insights.sbomify.com/CVE-2023-23637/index.md)
```

## Sources

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

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