An issue was discovered on Mitsubishi Electric Europe B.V.

published 2019-10-28 7y ago modified 2026-06-17 4mo ago also EUVD-2019-6023

cvss: 6.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.3%; EPSS 1.3% chance of exploitation in 30 days, percentile 69%
public exploits: 0; none known

An issue was discovered on Mitsubishi Electric Europe B.V. ME-RTU devices through 2.02 and INEA ME-RTU devices through 3.0. A world-readable /usr/smartrtu/init/settings.xml configuration file on the file system allows an attacker to read sensitive configuration settings such as usernames, passwords, and other sensitive RTU data due to insecure permission assignment.

Is CVE-2019-14925 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-21-252-03 updated 2021-09-09 cvss 6.5

Mitsubishi Electric Europe B.V. smartRTU and INEA ME-RTU

Mitsubishi Electric smartRTU and INEA ME-RTU < 3.3
affected: mitigation “Mitsubishi Electric Europe B.V. recommends users update to firmware Version 3.3 or later.” inea.si

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.26% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

mogozobo.com https://www.mogozobo.com/?p=3593 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness

CWE-276 Incorrect Default Permissions

References

mogozobo.com /?p=3593
exploit, third-party-advisory
mogozobo.com /
third-party-advisory

Sources

CVE List CVE-2019-14925
NVD CVE-2019-14925

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.