dbcve.org
Plc EditorApplication · We Con

CVE-2018-14792

MEDIUM · 6.3 CVSS v3.0 Published 2018-09-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
WECON PLC Editor version 1.3.3U may allow an attacker to execute code under the current process when processing project files.

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 confidence

WECON PLC Editor version 1.3.3U contains a vulnerability when processing project files that allows an attacker to execute arbitrary code under the current process context. This is a code execution vulnerability in the project's file parsing/loading mechanism, likely triggered by a specially crafted malicious project file.

MitigationApply vendor patch when available. Until then, restrict usage of untrusted project files, implement network segmentation for ICS environments, and consider application whitelisting to mitigate code execution risks.

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
Plc EditorApplication
Affected:= 1.3.3u

CVSS 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
Low
Integrity
Low
Availability
Low

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate WECON PLC Editor installation
    Search for 'PLC Editor' or 'WECON' in your system programs, or check common installation paths such as C:\Program Files\WECON or C:\Program Files (x86)\WECON
    Affected if The software is not installed on the system
  2. Identify installed version
    Open the PLC Editor application, then navigate to Help > About or check the version displayed in the application window. Alternatively, right-click the executable file and view Properties > Details for the version number
    Affected if The installed version is exactly 1.3.3U (case-insensitive match)
  3. Confirm project file usage
    Check if the PLC Editor is used to open or load project files (.plc, .pep, or vendor-specific project file formats)
    Affected if The application is used to open project files and the version is 1.3.3U

You are affected if WECON PLC Editor version 1.3.3U is installed and is used to load or open project files, as the vulnerability resides in the project's file parsing mechanism.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch when available. Until then, restrict usage of untrusted project files, implement network segmentation for ICS environments, and consider application whitelisting to mitigate code execution risks.

Fix this in Plc Editor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-14792 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-14792 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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