dbcve.org
SharecareApplication · Echobh

CVE-2021-36121

HIGH · 8.8 CVSS v3.1 Published 2021-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 Echo ShareCare 8.15.5. The file-upload feature in Access/DownloadFeed_Mnt/FileUpload_Upd.cfm is susceptible to an unrestricted upload vulnerability via the name1 parameter, when processing remote input from an authenticated user, leading to the ability for arbitrary files to be written to arbitrary filesystem locations via ../ Directory Traversal on the Z: drive (a hard-coded drive letter where ShareCare application files reside) and remote code execution as the ShareCare service user (NT AUTHORITY\SYSTEM).

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

Echo ShareCare 8.15.5 contains an unrestricted file upload vulnerability in Access/DownloadFeed_Mnt/FileUpload_Upd.cfm. The name1 parameter accepts remote input from authenticated users without validation, allowing directory traversal via ../ sequences to write arbitrary files to the Z: drive (where ShareCare files reside). This enables remote code execution as NT AUTHORITY\SYSTEM.

MitigationImplement strict input validation on the name1 parameter to reject directory traversal sequences and restrict file uploads to whitelisted file types and allowed directories. Validate all user-supplied paths server-side before file operations.

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
SharecareApplication
Affected:= 8.15.5

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Confirm ShareCare installation and version
    Locate the Echobh ShareCare application and identify the installed version. Check installation directories, about pages, or configuration files for version number 8.15.5.
    Affected if The installed version is Echobh ShareCare version 8.15.5.
  2. Verify vulnerable file exists
    Inspect the web server document root for the file Access/DownloadFeed_Mnt/FileUpload_Upd.cfm. This ColdFusion component handles file uploads and is the attack vector.
    Affected if The file FileUpload_Upd.cfm exists in the Access/DownloadFeed_Mnt directory on the web server.
  3. Check application authentication status
    Determine whether the ShareCare web application is configured to require authentication for the file upload functionality. Attempt to access the upload endpoint to see if authentication is enforced.
    Affected if The file upload endpoint is accessible to authenticated users, and the application accepts user credentials.
  4. Verify Z: drive availability
    Check if the Z: drive letter is mapped and accessible on the server hosting ShareCare. This is where ShareCare files are stored and where the vulnerability allows arbitrary file writes.
    Affected if The Z: drive exists and is accessible from the ShareCare server environment.

An environment is affected if it runs Echobh ShareCare version 8.15.5 with the FileUpload_Upd.cfm component accessible to authenticated users and the Z: drive available for file writes.

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 strict input validation on the name1 parameter to reject directory traversal sequences and restrict file uploads to whitelisted file types and allowed directories. Validate all user-supplied paths server-side before file operations.

Fix this in Sharecare Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing5.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-36121 — 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-2021-36121 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