CVE-2017-5569
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 · uneditedAn issue was discovered in eClinicalWorks Patient Portal 7.0 build 13. This is a blind SQL injection within the template.jsp, which can be exploited without the need of authentication and via an HTTP POST request, and which can be used to dump database data out to a malicious server, using an out-of-band technique such as select_loadfile().
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 confidenceBlind SQL injection vulnerability in template.jsp of eClinicalWorks Patient Portal 7.0 build 13. Exploitable via HTTP POST requests without authentication, allowing attackers to dump database contents using out-of-band techniques like select_loadfile().
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= 7.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify eClinicalWorks Patient Portal installationCheck the web application directory or installed software list for eClinicalWorks Patient Portal version 7.0. Review application banners, version info pages, or installer records to confirm the exact version and build number (build 13).Affected if The environment has eClinicalWorks Patient Portal version 7.0 installed, particularly build 13.
-
Locate template.jsp fileSearch the web application deployment directory for a file named template.jsp. This is the specific vulnerable component mentioned in the CVE.Affected if The file template.jsp exists in the patient portal web directory.
-
Verify unauthenticated POST accessTest if the patient portal endpoint for template.jsp accepts unauthenticated HTTP POST requests. This can be done by reviewing access control configuration or attempting a benign POST request to the template.jsp endpoint.Affected if The template.jsp endpoint allows unauthenticated POST requests without requiring authentication.
-
Check network exposureReview firewall rules and network access controls to determine if the patient portal HTTP/HTTPS ports are accessible from untrusted networks or the public internet.Affected if The patient portal is directly accessible from untrusted networks without VPN or additional authentication layers.
The environment is affected if eClinicalWorks Patient Portal version 7.0 (build 13) is installed with template.jsp exposed to unauthenticated network access.
Generated from the published advisory. Verify against your own configuration.
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 dataImmediately restrict network exposure of the patient portal and implement WAF rules for SQL injection detection. Contact eClinicalWorks for an official patch and conduct thorough code review of all JSP files for similar injection flaws.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5569 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-5569 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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