CVE-2020-7810
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 · uneditedhslogin2.dll ActiveX Control in Groupware contains a vulnerability that could allow remote files to be downloaded and executed by setting the arguments to the activex method. This is due to a lack of integrity verification of the policy files referenced in the update process, and a remote attacker could induce a user to crafted web page, causing damage such as malicious code infection.
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 confidenceThe hslogin2.dll ActiveX Control in Groupware contains a vulnerability allowing remote file download and execution by manipulating arguments to the ActiveX method. The root cause is the lack of integrity verification for policy files referenced during the update process, enabling attackers to inject malicious content that gets executed on vulnerable 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<= 6.7.8.4>= 7.0.0, <= 7.3.4CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Locate the hslogin2.dll file on the systemSearch for hslogin2.dll using the file explorer search or command: `dir /s C:\hslogin2.dll` on Windows systems. Check common installation directories such as C:\Program Files\Handysoft or the application directory.Affected if The file exists on the system, indicating the ActiveX control is present.
-
Determine the installed version of hslogin2.dllRight-click the file, select Properties, and view the Details tab to see the File Version. Alternatively, use PowerShell: `(Get-Item C:\path\to\hslogin2.dll).VersionInfo.FileVersion`Affected if The version falls within the affected ranges: <= 6.7.8.4 OR >= 7.0.0 through <= 7.3.4.
-
Check if the ActiveX control is registered in WindowsOpen the Windows Registry Editor and navigate to `HKLM\SOFTWARE\Microsoft\Code Store Database\Distribution Units` or `HKCU\SOFTWARE\Microsoft\Code Store Database\Distribution Units` for registered ActiveX controls. Look for entries containing hslogin2.dll or Hslogin2.Affected if The control is registered as an ActiveX component, making it loadable by browsers.
-
Inspect browser add-ons for the vulnerable controlIn Internet Explorer, go to Manage Add-ons and look for Handysoft Hslogin2 or hslogin2.dll. For Edge Legacy, navigate to about:addons. Check if the control is enabled.Affected if The hslogin2.dll ActiveX control is listed and enabled in any browser.
-
Verify the update mechanism configurationExamine the application or web application configuration files that reference policy file locations. Look for HTTP/HTTPS URLs pointing to policy files used during the update process.Affected if Policy files are fetched over unencrypted or unauthenticated channels without integrity verification.
The system is affected if hslogin2.dll version is <= 6.7.8.4 or between 7.0.0 and 7.3.4 inclusive, and the ActiveX control is present and registered on the system.
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 dataDisable or remove the vulnerable hslogin2.dll ActiveX control until a patch is available, implement cryptographic integrity verification (e.g., code signing and hash validation) for all policy files in the update process, and educate users to avoid untrusted websites.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7810 — 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-2020-7810 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