Skip to content

Vendor

wecon vulnerabilities

12 published CVES affecting wecon, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
12
Critical
1
High
8
Medium
3
Low
0
Unscored
0
CISA KEV
0
Atom feed of wecon alerts

Products

Latest wecon CVEs

Newest publication first

  1. HighCVSS 7.8 EPSS 8.6%

    WECON LeviStudioU Versions 2019-09-21 and prior are vulnerable to a stack-based buffer overflow, which may allow an attacker to remotely execute code.

  2. HighCVSS 7.8 EPSS 7.6%

    WECON LeviStudioU Versions 2019-09-21 and prior are vulnerable to a heap-based buffer overflow, which may allow an attacker to remotely execute code.

  3. HighCVSS 7.8 EPSS 2.9%

    WECON LeviStudioU Versions 2019-09-21 and prior are vulnerable to multiple stack-based buffer overflow instances while parsing project files, which may allow an attacker to execute arbitrary code.

  4. HighCVSS 7.8 EPSS 1.0%

    PLC Editor Versions 1.3.8 and prior is vulnerable to a stack-based buffer overflow while processing project files, which may allow an attacker to execute arbitrary code.

  5. HighCVSS 7.8 EPSS 0.97%

    PLC Editor Versions 1.3.8 and prior is vulnerable to an out-of-bounds write while processing project files, which may allow an attacker to execute arbitrary code.

  6. MediumCVSS 5.3 EPSS 1.2%

    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 dis...

  7. HighCVSS 8.8 EPSS 1.7%

    WECON Technology Co., Ltd. PI Studio HMI versions 4.1.9 and prior and PI Studio versions 4.2.34 and prior parse files and pass invalidated user data to an unsafe method call, which may allow code to be executed in the context of an administrator.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.