dbcve.org
XshellApplication · Netsarang

CVE-2021-37326

MEDIUM · 5.3 CVSS v3.1 Published 2021-08-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
NetSarang Xshell 7 before Build 0077 includes unintended code strings in paste operations.

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 · moderate confidence

NetSarang Xshell 7 before Build 0077 contains unintended code strings that are included in paste operations. When users copy and paste content, hidden or embedded code strings may be inadvertently processed or transmitted, potentially leading to code execution or data leakage through the clipboard.

MitigationUpgrade Xshell to Build 0077 or later to remediate this vulnerability. Organizations should verify current installations and deploy the updated version across affected systems.

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
XshellApplication
Affected:= 7

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Verify Xshell 7 is installed
    Locate the Xshell application on the system - typically in Program Files or check Windows Programs and Features. Confirm the product name shows 'Xshell 7'.
    Affected if Xshell 7 is installed on the system
  2. Identify the installed build version
    Open Xshell 7 and navigate to Help > About, or right-click the Xshell icon and select About. Record the exact build number displayed (e.g., Build 0072, Build 0076).
    Affected if The build number shown is lower than 0077
  3. Compare build against affected range
    If you cannot access the About dialog, check the Xshell executable properties by right-clicking the Xshell.exe file in the installation directory and viewing the Details tab for version information.
    Affected if The version or build is 7.x with a build number prior to 0077

The user is affected if Xshell version 7 is installed with any build number below 0077, as these versions contain unintended code strings that may execute or leak data through clipboard paste operations.

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

Upgrade Xshell to Build 0077 or later to remediate this vulnerability. Organizations should verify current installations and deploy the updated version across affected systems.

Fix this in Xshell 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-2021-37326 — 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-37326 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