CVE-2018-19002

HIGHNVD 7.87.8—

7.8

LCDS Laquis SCADA prior to version 4.1.0.4150 allows improper control of generation of code when opening a specially crafted project file, which may allow remote code execution, data exfiltration, or cause a system crash.

CVSS v3: 7.8
EG Score: 7.8(medium)
EPSS: 64.9%
KEV: Not listed

Published

February 5, 2019

Last Modified

November 21, 2024

References (4)

ics-cert@hqhttp://www.securityfocus.com/bid/106634
ics-cert@hqhttps://ics-cert.us-cert.gov/advisories/ICSA-19-015-01
af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/106634
af854a3a-2127-422b-91ae-364da2661108https://ics-cert.us-cert.gov/advisories/ICSA-19-015-01

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-94Improper Control of Generation of Code (Code Injection)

Data Freshness Timeline

(refreshed 10× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-05 22:45 UTCepss_batch
2026-06-05 22:45 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-04 13:10 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 22:45 UTCEG score recompute
2026-05-27 22:45 UTCGHSA enrichment
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2018-19002?

CVE-2018-19002 is a high vulnerability published on February 5, 2019. LCDS Laquis SCADA prior to version 4.1.0.4150 allows improper control of generation of code when opening a specially crafted project file, which may allow remote code execution, data exfiltration, or cause a system crash.

When was CVE-2018-19002 disclosed?

CVE-2018-19002 was first published in the National Vulnerability Database on February 5, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2018-19002 actively exploited?

CVE-2018-19002 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 64.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2018-19002?

CVE-2018-19002 has a CVSS v3 base score of 7.8 (NVD).

How do I remediate CVE-2018-19002?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-19002, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-19002

Explore →

Is Your Infrastructure Affected by CVE-2018-19002?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2018-19002

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2018-19002?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)