Skip to content
Fencer Vulns
high 7.8

CVE-2018-7530 json

Parsing malformed project files in Omron CX-One versions 4.42 and prior, including the following applications: CX-FLnet versions 1.00 and p…

published 2018-04-17 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-19259

cvss
7.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 25%
public exploits
0
none known

Summary

Parsing malformed project files in Omron CX-One versions 4.42 and prior, including the following applications: CX-FLnet versions 1.00 and prior, CX-Protocol versions 1.992 and prior, CX-Programmer versions 9.65 and prior, CX-Server versions 5.0.22 and prior, Network Configurator versions 3.63 and prior, and Switch Box Utility versions 1.68 and prior, may allow the pointer to call an incorrect object resulting in an access of resource using incompatible type condition.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-18-100-02 updated cvss 5.3

Omron CX-One

  • Omron CX-FLnet <= 1.00 Omron CX-One <=4.42 Omron CX-Programmer <= 9.65 Omron CX-Protocol <= 1.992 Omron CX-Server <= 5.0.22 Omron Network Configurator <= 3.63
    +1 more products
    Omron Switch Box Utility <= 1.68
    affected: vendor fix, mitigation “CX-FLnet version 1.10,”

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

CVSS scores

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

Affected products

  • ICS-CERT Omron CX-One

Classification

Weakness
  • CWE-843 Access of Resource Using Incompatible Type
  • CWE-118 Incorrect Access of Indexable Resource

References

Sources

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.