CVE-2018-14810
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWECON 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceWECON PI Studio HMI and PI Studio software contain a code execution vulnerability where file parsing functions fail to properly validate user-supplied data before passing it to unsafe method calls. This allows attackers to execute arbitrary code with administrator privileges by convincing a user to open a specially crafted malicious file.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 4.2.34<= 4.1.9CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check WeCon Pi Studio versionOpen Windows Control Panel > Programs and Features, locate 'WeCon Pi Studio' or similar entry, and note the installed version. Alternatively, right-click the application executable in the program installation folder, select Properties, and view the File Version on the Details tab.Affected if The version listed is 4.2.34 or lower
-
Check WeCon Pi Studio HMI versionOpen Windows Control Panel > Programs and Features, locate 'WeCon Pi Studio Hmi' or similar entry, and note the installed version. Alternatively, check the executable properties as described above.Affected if The version listed is 4.1.9 or lower
-
Identify file parsing componentsLocate the main application executable (commonly named PIStudio.exe, PiStudio.exe, or similar in the installation directory). Note that file parsing functionality is built into the software and activates when opening project files with extensions such as .pi, .project, or proprietary HMI project formats.Affected if The identified executable belongs to a version within the affected ranges and the software can open project files (standard functionality)
-
Verify vulnerable version is actively installedConfirm the software is actually installed and not just present as a residual folder. Check that the executable exists and can be launched. Use 'wmic product get name,version' or 'Get-WmiObject Win32_Product' in PowerShell to query installed software inventory.Affected if The software appears in the installed programs list with a version matching the affected ranges
A user is affected if WeCon Pi Studio version 4.2.34 or lower, or WeCon Pi Studio HMI version 4.1.9 or lower, is installed and the file parsing functionality can be used to open project files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate PI Studio HMI to version 4.1.10 or later and PI Studio to version 4.2.35 or later. Until patched, avoid opening untrusted project files from untrusted sources.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14810 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-14810 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data