Skip to content
Fencer Intel
medium 5.5

CVE-2019-10976 json

Mitsubishi Electric FR Configurator2, Version 1.16S and prior.

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

cvss
5.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits
0
none known

Summary

Mitsubishi Electric FR Configurator2, Version 1.16S and prior. This vulnerability is triggered when input passed to the XML parser is not sanitized while parsing the XML project and/or template file (.frc2). Once a user opens the file, the attacker could read arbitrary files.

Patch / fix

  • mitsubishielectric electric_fr_configurator2_firmware 1.16s

Is CVE-2019-10976 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-204-01 updated cvss 7.1

Mitsubishi Electric FR Configurator2

  • Mitsubishi Electric FR Configurator2 <= 1.16S
    affected: mitigation “Mitsubishi Electric has released Version 1.17T for the reported vulnerabilities. Additional information about the vulnerabilities and how to obtain the update can be found at the following location:” mitsubishielectric.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

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

CVSS scores

assigned by version score vector
NVD 3.0 5.5 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N

Affected products

  • Mitsubishi Electric Mitsubishi Electric FR Configurator2

Classification

Weakness
  • CWE-611 Improper Restriction of XML External Entity Reference

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.