XplatformApplication · Tobesoft

CVE-2020-7806

CRITICAL · 9.8 CVSS v3.1 Published 2020-05-06
Fix available
A fix is available. Upgrade to after 9.2.2.250 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Tobesoft Xplatform 9.2.2.250 and earlier version have an arbitrary code execution vulnerability by using method supported by Xplatform ActiveX Control. It allows attacker to cause remote code execution.

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

Tobesoft Xplatform versions 9.2.2.250 and earlier contain a critical arbitrary code execution vulnerability in the Xplatform ActiveX Control. Attackers can exploit a specific method supported by this ActiveX control to achieve remote code execution on affected systems. The CVSS 9.8 score indicates trivial exploitability with complete compromise of confidentiality, integrity, and availability.

MitigationApply vendor-supplied patches for Xplatform to a version newer than 9.2.2.250. Until patched, disable ActiveX controls in browsers, deploy EMET or Windows Defender Exploit Guard, and restrict execution of untrusted ActiveX content through browser security settings or application whitelisting.

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
XplatformApplication
Affected:<= 9.2.2.250

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
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 checks

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

  1. Check if Tobesoft Xplatform is installed
    Search for Xplatform in installed programs via Windows Control Panel > Programs and Features, or use command: reg query 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall' /s /f Xplatform
    Affected if Tobesoft Xplatform appears in installed programs
  2. Determine the installed Xplatform version
    Locate the Xplatform installation directory (typically under C:\Program Files\Tobesoft or C:\Program Files (x86)\Tobesoft) and check the file properties of the main executable, or check the version via: wmic product where "name like '%Xplatform%'" get version
    Affected if The installed version is 9.2.2.250 or any version lower than 9.2.2.250
  3. Verify the ActiveX control is registered
    Check for the Xplatform ActiveX control registration in the Windows Registry under HKLM\SOFTWARE\Classes\CLSID or HKCU\SOFTWARE\Classes\CLSID, searching for CLSIDs containing 'Xplatform' or related identifiers
    Affected if The Xplatform ActiveX control CLSID is present in the registry
  4. Confirm the vulnerable ActiveX method is exposed
    Use OLE/COM Object Viewer (oleview.exe) or examine the ActiveX control's type library to list available methods, or inspect the control's DLL/OCX file in the Xplatform installation directory
    Affected if The ActiveX control exposes methods that can be invoked from browser or script contexts
  5. Check if browsers have ActiveX controls enabled
    In Internet Explorer, verify ActiveX settings under Internet Options > Security > Custom Level > ActiveX controls and plugins; for other browsers, note that IE-based rendering may still be used by Xplatform applications
    Affected if ActiveX controls are allowed to run or IE Mode is in use

A system is affected if Tobesoft Xplatform version 9.2.2.250 or lower is installed and the Xplatform ActiveX control is registered and accessible

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
Upgrade available Upgrade to a release after 9.2.2.250
Interim mitigation

Apply vendor-supplied patches for Xplatform to a version newer than 9.2.2.250. Until patched, disable ActiveX controls in browsers, deploy EMET or Windows Defender Exploit Guard, and restrict execution of untrusted ActiveX content through browser security settings or application whitelisting.

Fix this in Xplatform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-7806 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-7806 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