dbcve.org
MikogoApplication

CVE-2019-12731

HIGH · 7.8 CVSS v3.0 Published 2019-07-12
Fix available
A fix is available. Upgrade to 5.10.2 or later.
See remediation →
80/100
Remediation priority · High
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
The Windows versions of Snapview Mikogo, versions before 5.10.2 are affected by insecure implementations which allow local attackers to escalate privileges.

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

Mikogo client for Windows versions prior to 5.10.2 contains insecure implementations that allow a local attacker to gain elevated (administrator) privileges on the affected system.

MitigationUpgrade Mikogo to version 5.10.2 or later. Identify all endpoints with older Mikogo installations and deploy the patched version through organizational patch management.

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
MikogoApplication
Affected:< 5.10.2

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/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 checks

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

  1. Verify Mikogo is installed on the Windows host
    Check for Mikogo installation by searching Program Files for the Mikogo folder, or query the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named Mikogo.
    Affected if Mikogo is found installed on the system.
  2. Retrieve the installed Mikogo version number
    Open the Windows registry key HKLM\SOFTWARE\Mikogo or HKLM\SOFTWARE\WOW6432Node\Mikogo and locate the Version value. Alternatively, right-click the Mikogo executable in the installation folder, select Properties, and view the Details tab.
    Affected if Unable to retrieve a version number indicates an unpatched or non-standard installation.
  3. Compare the installed version against the vulnerable range
    Take the retrieved version number and compare it numerically to 5.10.2. Any version lower than 5.10.2 (for example, 5.10.1, 5.9.0, 4.x) is considered vulnerable.
    Affected if The installed version is below 5.10.2.

A Windows system running Mikogo client with version lower than 5.10.2 is affected by this privilege escalation vulnerability.

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 5.10.2 or later
Fixed in 5.10.2
Interim mitigation

Upgrade Mikogo to version 5.10.2 or later. Identify all endpoints with older Mikogo installations and deploy the patched version through organizational patch management.

Fix this in Mikogo Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-12731 — 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-2019-12731 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