CVE Tools

Description

An issue was discovered on Mitsubishi Electric Europe B.V. ME-RTU devices through 2.02 and INEA ME-RTU devices through 3.0. An unauthenticated remote OS Command Injection vulnerability allows an attacker to execute arbitrary commands on the RTU due to the passing of unsafe user supplied data to the RTU's system shell. Functionality in mobile.php provides users with the ability to ping sites or IP addresses via Mobile Connection Test. When the Mobile Connection Test is submitted, action.php is called to execute the test. An attacker can use a shell command separator (;) in the host variable to execute operating system commands upon submitting the test data.

In plain language

AI Act now

CVE-2019-14931 is a serious flaw in certain Mitsubishi Electric ME-RTU devices that lets an attacker run commands over the network without logging in; if you use these units and they’re reachable, you should treat it as urgent—there’s no known patch version provided.

Executive summary

CVE-2019-14931 is an unauthenticated remote OS Command Injection in Mitsubishi Electric ME-RTU “Mobile Connection Test” handling (mobile.php calls backend action.php), where an attacker can manipulate the `host` input (e.g., using shell separators like `;`) to execute arbitrary commands on the device.

If affected, business impact
Full device takeoverSensitive device data theftConfiguration tamperingOperational disruption

What to do now

  1. Check whether you run Mitsubishi Electric ME-RTU devices (“smartrtu firmware” and “me-rtu firmware”) and identify whether they are on versions through 2.02 (ME-RTU) or through 3.0 (INEA ME-RTU).
  2. Verify whether the “Mobile Connection Test” feature is reachable from the network, and whether the related endpoints (mobile.php / action.php) are exposed (directly or indirectly) from anywhere outside your trusted network.
  3. If the device is reachable, immediately isolate it from the internet and untrusted networks (firewall/VPN segmentation) so attackers can’t reach the vulnerable feature.
  4. Contact Mitsubishi Electric support or your integrator and ask for a confirmed fixed firmware version for CVE-2019-14931, since no patch information is available in the provided advisories.
  5. Create an incident response plan for ME-RTU compromise: preserve logs/config, review for unexpected outbound connections or system command activity, and prepare to restore known-good configuration if tampering is found.
May need vendor / contractor work

CVSS Vector Breakdown

AV:NAC:LPR:NUI:NS:UC:HI:HA:H
Exploitability
AV:NAttack Vector
Network
AC:LAttack Complexity
Low
PR:NPrivileges Required
None
UI:NUser Interaction
None
Scope
S:UScope
Unchanged
Impact
C:HConfidentiality
High
I:HIntegrity
High
A:HAvailability
High

Weaknesses

Affected Products

mitsubishielectric
commercial·JPaka mitsubishi electric
inea
commercialaka me-rtu firmware, inea me-rtu
and 1 more affected products View all →

Exploitability

No known exploits, KEV entries, or remediation guidance available for this vulnerability yet.

Attack Graph

Products CVE Techniques Tactics

Click technique nodes for MITRE ATT&CK details · drag to pan · Ctrl/ + scroll to zoom, or go fullscreen.

MITRE ATT&CK

1 technique
Execution
View detailed technique mapping

References

and 15 more references View all →
3

Unlock Complete Vulnerability Intelligence

Get the full picture for CVE-2019-14931 and every CVE in our database. Create a free account — no credit card required.

Create Free Account
Plain-language analysis
Impact assessment and exploitation scenario in plain English
Attack graph visualization
Interactive attack path and kill chain mapping
Exploit details & PoC links
ExploitDB, Metasploit, GitHub PoCs with direct links
Nuclei scanner templates
Ready-to-use vulnerability scanner templates
Full remediation guide
Patch instructions, workarounds, and compliance impact
Interactive AI chat
Ask questions about this vulnerability in natural language
Related vulnerabilities
Semantically similar CVEs and attack patterns
REST API & MCP access
Integrate vulnerability data into your workflows