CVE-2021-36122
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 Echo ShareCare 8.15.5. The UnzipFile feature in Access/EligFeedParse_Sup/UnzipFile_Upd.cfm is susceptible to a command argument injection vulnerability when processing remote input in the zippass parameter from an authenticated user, leading to the ability to inject arbitrary arguments to 7z.exe.
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 confidenceEcho ShareCare 8.15.5 contains a command argument injection vulnerability in the UnzipFile feature of Access/EligFeedParse_Sup/UnzipFile_Upd.cfm. The zippass parameter, when supplied by an authenticated user, is passed to 7z.exe without proper sanitization, allowing injection of arbitrary arguments.
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= 8.15.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Echo ShareCare versionLocate the version information for your Echo ShareCare installation. This is typically found in the application itself, in an about page, or in installation/configuration files. Compare the version number to 8.15.5.Affected if The installed version is exactly 8.15.5
-
Locate the vulnerable UnzipFile componentSearch for the file UnzipFile_Upd.cfm within the Access/EligFeedParse_Sup directory on your web server or application installation path.Affected if The file Access/EligFeedParse_Sup/UnzipFile_Upd.cfm exists in your installation
-
Verify the UnzipFile feature is accessibleCheck if the UnzipFile feature endpoint is exposed in your web application. This typically involves checking web server logs or accessible URL paths under the Access module.Affected if The UnzipFile feature is accessible via web request without additional access controls blocking it
-
Inspect zippass parameter handlingExamine the UnzipFile_Upd.cfm code to see how the zippass parameter is processed. Look for direct concatenation of this parameter into system command calls.Affected if The zippass parameter is passed directly to 7z.exe without input validation or sanitization
-
Confirm 7z.exe is present on the systemLocate the 7z.exe executable that the application uses for zip operations. This is typically found in the application bin directory or a designated utilities folder.Affected if 7z.exe exists and is used by the vulnerable component
You are affected if you are running exactly version 8.15.5 and the UnzipFile_Upd.cfm component with its zippass parameter handling is exposed and passes user input directly to 7z.exe.
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 dataImplement strict input validation on the zippass parameter to reject any special characters, or refactor the code to avoid passing user input directly to system commands entirely.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-36122 — 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-2021-36122 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