# CVE-2021-40374: Cross-site scripting in n/a

> Remote attackers can inject arbitrary scripts via patient address fields in OpenEyes, leading to script execution when profiles are viewed.

- **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:** 6 Apr 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6f7g-fvmv-x9vc

## What is CVE-2021-40374?

CVE-2021-40374 is a medium-severity cross-site scripting vulnerability in n/a, published on 6 Apr 2022. 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 was identified in Apperta Foundation OpenEyes 3.5.1. Updating a patient's details allows remote attackers to inject arbitrary web script or HTML via the Address1 parameter. This JavaScript then executes when the patient profile is loaded, which could be used in a XSS attack.

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

## Which versions are affected by CVE-2021-40374?

It affects 1 product.


Products: Apperta Openeye.

## How do I fix CVE-2021-40374?

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

## Is CVE-2021-40374 being exploited?

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

Public exploit code:

- Stored Cross-site Scripting in OpenEyes 3.5.1 (github_poc): https://github.com/DCKento/CVE-2021-40374

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-40374 and fix it if it is affected.

What it is: CVE-2021-40374 is a medium-severity cross-site scripting vulnerability in n/a, published on 6 Apr 2022. 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-2021-40374 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-2021-40374/ (Markdown: https://insights.sbomify.com/CVE-2021-40374/index.md)
```

## Sources

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

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