# CVE-2017-5599: Cross-site scripting in n/a

> Reflected XSS in eClinicalWorks Patient Portal allows attackers to execute scripts in victims' browsers via the race parameter, potentially stealing data or hijacking sessions.

- **Severity:** Medium 6.1 (`CVSS:3.0/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:** 27 Jan 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4g8v-wmw6-8v54

## What is CVE-2017-5599?

CVE-2017-5599 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 Jan 2017. 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

An issue was discovered in eClinicalWorks Patient Portal 7.0 build 13. This is a reflected Cross Site Scripting vulnerability which affects the raceMasterList.jsp page within the Patient Portal. Inserted payload is rendered within the Patient Portal and the raceMasterList.jsp page does not require authentication. The vulnerability can be used to extract sensitive information or perform attacks against the user's browser. The vulnerability affects the raceMasterList.jsp page and the following parameter: race.

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

## Which versions are affected by CVE-2017-5599?

It affects 1 product.


Products: Eclinicalworks Patient Portal.

## How do I fix CVE-2017-5599?

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

## Is CVE-2017-5599 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-5569](https://insights.sbomify.com/CVE-2017-5569/): SQL injection in n/a (critical 9.8)
- [CVE-2017-5570](https://insights.sbomify.com/CVE-2017-5570/): SQL injection in n/a (high 8.8)
- [CVE-2017-5598](https://insights.sbomify.com/CVE-2017-5598/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5599 and fix it if it is affected.

What it is: CVE-2017-5599 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 Jan 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-5599 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-2017-5599/ (Markdown: https://insights.sbomify.com/CVE-2017-5599/index.md)
```

## Sources

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

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