CVE-2018-17889 json
In WECON Technology Co., Ltd.
published 8y ago modified 4mo ago also EUVD-2018-9630
- cvss
- 5.3
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 69%
- public exploits
- 0
- none known
Summary
In WECON Technology Co., Ltd. PI Studio HMI versions 4.1.9 and prior and PI Studio versions 4.2.34 and prior when parsing project files, the XMLParser that ships with Wecon PIStudio is vulnerable to a XML external entity injection attack, which may allow sensitive information disclosure.
Is CVE-2018-17889 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-18-277-01 updated cvss 5.5
WECON PI Studio (Update A)
-
WECON PI Studio <= 4.2.125 WECON PI Studio HMI <= 4.1.9affected: mitigation “WECON has verified these vulnerabilities but has not yet released an updated version. CISA is working with WECON and will update this advisory once an updated version is released.”
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.25% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.3 | CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Affected products
- WECON PI Studio HMI
- WECON PI Studio
Classification
- Weakness
-
- CWE-611 Improper Restriction of XML External Entity Reference
References
-
ics-cert.us-cert.gov
/advisories/ICSA-18-277-01
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2018-17889
- NVD CVE-2018-17889
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.