Skip to content
Fencer Intel
high 7.8

CVE-2019-6566 json

GE Communicator, all versions prior to 4.0.517, allows a non-administrative user to replace the uninstaller with a malicious version, which…

published 7y ago modified 4mo ago also EUVD-2019-16125

cvss
7.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 27%
public exploits
0
none known

Summary

GE Communicator, all versions prior to 4.0.517, allows a non-administrative user to replace the uninstaller with a malicious version, which could allow an attacker to gain administrator privileges to the system.

Patch / fix

  • ge ge_communicator 4.0.517

Is CVE-2019-6566 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-19-122-02 updated cvss 7.3

GE Communicator

  • General Electric (GE) Communicator Application < 4.0.517 General Electric (GE) Communicator Installer < 4.0.517 General Electric (GE) Communicator MeterManager < 4.0.517 General Electric (GE) Communicator PostGreSQL < 4.0.517 General Electric (GE) Communicator WISE Uninstaller < 4.0.517
    affected: mitigation “GE recommends users upgrade to GE Communicator version 4.0.517 or newer, which can be downloaded from the following link:” gegridsolutions.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.2 AV:L/AC:L/Au:N/C:C/I:C/A:C

Affected products

  • n/a GE Communicator

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.