A buffer overflow can be triggered in LeviStudio HMI Editor, Version 1.10 part of Wecon LeviStudioU 1.8.29, and PI Studio HMI Project Progr…

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

cvss: 5.3; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits: 0; none known

A buffer overflow can be triggered in LeviStudio HMI Editor, Version 1.10 part of Wecon LeviStudioU 1.8.29, and PI Studio HMI Project Programmer, Build: November 11, 2017 and prior by opening a specially crafted file.

Vendor advisories

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

cisa ICSA-18-116-02 updated 2018-04-26 cvss 5.9

WECON Technology Co., Ltd. LeviStudio HMI Editor and PI Studio HMI Project Programmer

WECON PI Studio HMI Project Programmer Build <=November 11, 2017 WECON LeviStudioU <=1.8.29
affected: mitigation “WECON recommends that users update to the latest version which can be found at the following location (download):”

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

CVSS scores

assigned by	version	score	vector
NVD	3.0	5.3	CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P

Affected products

WECON Technology Co., Ltd. LeviStudio HMI Editor
WECON Technology Co., Ltd. PI Studio HMI Project Programmer

Classification

Weakness

CWE-121 Stack-based Buffer Overflow
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

securityfocus.com /bid/104016
vdb-entry, third-party-advisory
ics-cert.us-cert.gov /advisories/ICSA-18-116-02
third-party-advisory, us-government-resource

Sources

CVE List CVE-2018-7527
NVD CVE-2018-7527

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.

Summary