Skip to content
Fencer Intel
critical 9.3

CVE-2013-2817 json

An ActiveX control in IcoLaunch.dll in Mitsubishi Electric Automation MC-WorX Suite 8.02 allows user-assisted remote attackers to execute a…

published 12y ago modified 4mo ago also EUVD-2013-2756

cvss
9.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
5.9%
EPSS 5.9% chance of exploitation in 30 days, percentile 93%
public exploits
1
Exploit-DB

Summary

An ActiveX control in IcoLaunch.dll in Mitsubishi Electric Automation MC-WorX Suite 8.02 allows user-assisted remote attackers to execute arbitrary programs via a crafted HTML document in conjunction with a Login Client button click.

Patch / fix

Is CVE-2013-2817 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-14-051-02 updated cvss 9.3

Mitsubishi Electric Automation MC-WorX Suite Unsecure ActiveX Control

  • Mitsubishi Electric MC-WorX Suite 8.02
    affected: mitigation “Mitsubishi Electric Automation, Inc has published a patch resolving this vulnerability available at the following URL (http://www.meau.com/eprise/main/sites/public/Products/Software/-MC_Works)”

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

Timeline

  1. First public exploit (EDB-28284)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-28284 Mitsubishi MC-WorkX 8.02 - ActiveX Control 'IcoLaunch' File Execution remote, 2013-09-15

CVSS scores

assigned by version score vector
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code

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.