dbcve.org
Patient PortalApplication · Eclinicalworks

CVE-2017-5599

MEDIUM · 6.1 CVSS v3.0 Published 2017-01-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A reflected Cross-Site Scripting (XSS) vulnerability exists in the raceMasterList.jsp page of eClinicalWorks Patient Portal 7.0 build 13. The vulnerability affects the 'race' parameter which is not properly sanitized before being rendered in the page output. This allows an attacker to inject malicious JavaScript that executes in the context of the victim's browser, potentially stealing session cookies or other sensitive information.

MitigationImplement proper input validation and output encoding for the 'race' parameter in raceMasterList.jsp to prevent XSS attacks. Consider using a web application firewall (WAF) as an additional layer of protection while the code fix is deployed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Patient PortalApplication
Affected:= 7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm eClinicalWorks Patient Portal installation
    Review your web server documentation or application inventory to identify if eClinicalWorks Patient Portal is deployed in your environment. Check the application banner, headers, or administrative interface for product identification.
    Affected if The system is running eClinicalWorks Patient Portal version 7.0 build 13
  2. Verify the specific version
    Access the administrative interface, check the software About page, review installation logs, or query the application for its version number. Compare against the affected version 7.0 (build 13).
    Affected if The installed version is exactly 7.0 (specifically build 13)
  3. Locate the vulnerable JSP page
    Attempt to access the URL path /raceMasterList.jsp on your Patient Portal web server. The exact path depends on your installation context (commonly under the web application root or portal directory).
    Affected if The raceMasterList.jsp page exists and is accessible via HTTP/HTTPS
  4. Test the race parameter for reflected XSS
    Send a crafted request to raceMasterList.jsp with a test payload in the 'race' parameter (for example: race=<script>alert('XSS')</script>). Inspect the response to see if the payload is reflected unencoded in the HTML output.
    Affected if The 'race' parameter value is returned in the response without proper HTML encoding or sanitization

You are affected if you are running eClinicalWorks Patient Portal version 7.0 build 13 and the raceMasterList.jsp page is accessible with the 'race' parameter reflecting unsanitized input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding for the 'race' parameter in raceMasterList.jsp to prevent XSS attacks. Consider using a web application firewall (WAF) as an additional layer of protection while the code fix is deployed.

Fix this in Patient Portal Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-5599 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-5599 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data