CVE-2019-18238 json
In Moxa ioLogik 2500 series firmware, Version 3.0 or lower, and IOxpress configuration utility, Version 2.3.0 or lower, sensitive informati…
published 2020-02-26 6 y ago modified 2026-06-17 4 mo ago also EUVD-2019-8037
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
In Moxa ioLogik 2500 series firmware, Version 3.0 or lower, and IOxpress configuration utility, Version 2.3.0 or lower, sensitive information is stored in configuration files without encryption, which may allow an attacker to access an administrative account.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-20-056-02 updated cvss 7.5
Moxa ioLogik 2542-HSPA Series Controllers and IOs, and IOxpress Configuration Utility
-
Moxa ioLogik 2500 series <= 3.0 Moxa IOxpress configuration utility <= 2.3.0affected: mitigation “Moxa has developed a solution to address these vulnerabilities: Please contact Moxa Technical Support for a security patch.” moxa.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
0.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- n/a Moxa ioLogik 2500 series firmware, Version 3.0 or lower, IOxpress configuration utility, Version 2.3.0 or lower
Classification
- Weakness
-
- CWE-312 Cleartext Storage of Sensitive Information
References
-
us-cert.gov
/ics/advisories/icsa-20-056-02
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2019-18238
- NVD CVE-2019-18238
Fencer Vulns 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.