CVE-2020-7820
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 · uneditedNexacro14/17 ExtCommonApiV13 Library under 2019.9.6 version contain a vulnerability that could allow remote attacker to execute arbitrary code by setting the arguments to the vulnerable API. This can be leveraged for code execution by rebooting the victim’s PC
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 ExtCommonApiV13 library in Nexacro14/17 versions prior to 2019.9.6 contains a remote code execution vulnerability. Attackers can exploit this by providing malicious arguments to the vulnerable API, achieving arbitrary code execution that persists through system reboot.
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< 2019.9.6< 2019.9.6CVSS 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.1/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 installed Nexacro productCheck system for presence of Nexacro 14 or Nexacro 17 applications or libraries. Look for software installation directories or check program files.Affected if Nexacro 14 or 17 is installed on the system
-
Locate ExtCommonApiV13 librarySearch for the ExtCommonApiV13.dll or ExtCommonApiV13 library file within the Nexacro installation directory or application folders.Affected if The ExtCommonApiV13 library file is found on the system
-
Determine library versionRight-click the ExtCommonApiV13 file, select Properties, and view the File Version or Product Version information. Alternatively, use command-line tools like 'wmic datafile' or PowerShell to query file version metadata.Affected if The extracted version is lower than 2019.9.6
-
Check application manifest or dependenciesIf the library version cannot be directly determined, check the application's manifest, dependency files, or runtime configuration that references ExtCommonApiV13 version information.Affected if Referenced version is below 2019.9.6
If Nexacro 14 or 17 is installed with an ExtCommonApiV13 library version prior to 2019.9.6, the environment is affected by this vulnerability.
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.
dbcve · scoped2019.9.6
Upgrade the ExtCommonApiV13 library to version 2019.9.6 or later to remediate this vulnerability.
Nexacro 14/17 version 2019.9.6 or later
- Identify the current Nexacro version in use (14 or 17) by checking the product documentation or system information
- Obtain the fixed version 2019.9.6 or later from the official vendor (Tobesoft) at support.tobesoft.co.kr
- Upgrade Nexacro 14 or Nexacro 17 to version 2019.9.6 or subsequent released version
- Verify the upgrade was successful by confirming the ExtCommonApiV13 Library version post-upgrade
- Test the application functionality to ensure the upgrade does not break existing features
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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 $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7820 — 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-7820 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