Skip to main content
CVE-2023-6943VulnerabilityPublished Updated

CVE-2023-6943: Mitsubishi Electric EZSocket · Unsafe Reflection

Affects Mitsubishi Electric EZSocketSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.1% chance of exploitation in 30 days – higher than 81% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Mitsubishi Electric Corporation EZSocketAffected
  • >=3.0 <=5.92
Fixed in–

AI-suggested

1. Immediate patching: Organizations should prioritize updating all affected Mitsubishi Electric products to the latest versions where the vulnerability is patched. If patches are not yet available, apply any vendor-recommended workarounds or mitigations. 2. Network segmentation: Isolate vulnerable devices and systems from general IT networks and restrict RPC access using firewalls and network access controls to limit exposure. 3. RPC filtering and monitoring: Implement strict filtering of RPC traffic to allow only trusted sources and monitor for anomalous RPC requests that could indicate exploitation attempts. 4. Application whitelisting: Use application control solutions to prevent unauthorized libraries or code from loading on systems running Mitsubishi Electric software. 5. Intrusion detection and prevention: Deploy IDS/IPS solutions tuned to detect exploitation attempts targeting unsafe reflection vulnerabilities. 6. Incident response readiness: Prepare and test incident response plans specific to industrial control system compromises, including backups and recovery procedures. 7. Vendor engagement: Maintain communication with Mitsubishi Electric for timely updates, patches, and guidance. 8. Asset inventory and risk assessment: Identify all affected products in the environment and assess risk exposure to prioritize remediation efforts.

Description

Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') vulnerability in Mitsubishi Electric Corporation EZSocket versions 3.0 to 5.92, GT Designer3 Version1(GOT1000) versions 1.325P and prior, GT Designer3 Version1(GOT2000) versions 1.320J and prior, GX Works2 versions 1.11M and later, GX Works3 versions 1.106L and prior, MELSOFT Navigator versions 1.04E to 2.102G, MT Works2 versions 1.190Y and prior, MX Component versions 4.00A to 5.007H and MX OPC Server DA/UA all versions allows a remote unauthenticated attacker to execute a malicious code by RPC with a path to a malicious library while connected to the products.

References

Community reviews

Loading reviews…