dbcve.org
Plc EditorApplication · We Con

CVE-2020-25181

HIGH · 8.8 CVSS v3.1 Published 2020-12-01
Fix available
A fix is available. Upgrade to after 1.3.8 or later.
See remediation →
95/100
Remediation priority · Urgent
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 Versions 1.3.8 and prior has a heap-based buffer overflow vulnerabilities have been identified that may allow arbitrary code execution.

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 versions 1.3.8 and prior contain a heap-based buffer overflow vulnerability. This memory corruption flaw can be exploited to achieve arbitrary code execution on the affected system.

MitigationUpdate WECON PLC Editor to a version newer than 1.3.8. If immediate updating is not feasible, restrict network access to the editor and isolate affected systems from untrusted networks.

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

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
High
Integrity
High
Availability
High

CVSS:3.1/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 checks

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

  1. Locate WECON PLC Editor installation directory
    Check common installation paths: C:\Program Files\WECON\PLC Editor or C:\Program Files (x86)\WECON\PLC Editor. If installed elsewhere, search for 'PLC Editor.exe' using: dir /s C:\PLC Editor.exe
    Affected if The software is found installed on the system
  2. Check executable version information
    Right-click on PLC Editor.exe, select Properties, then go to the Details tab. Note the File Version or Product Version value.
    Affected if The version displayed is 1.3.8 or lower (e.g., 1.3.8, 1.3.7, 1.3.6, etc.)
  3. Query version via command line
    Open Command Prompt and run: wmic product where "name like '%PLC Editor%'" get version,name. Alternatively, use: powershell (Get-Item 'C:\Program Files\WECON\PLC Editor\PLC Editor.exe').VersionInfo
    Affected if The reported version is 1.3.8 or any version lower than 1.3.8
  4. Verify exact version match
    If version shows as 1.3.8 or includes 1.3.8 (such as 1.3.8.0, 1.3.8.1, 1.3.8 SP1), this matches the vulnerable version range.
    Affected if Version string contains 1.3.8 or falls below it (e.g., 1.3.7, 1.3.6, 1.3.5)

The system is affected if WECON PLC Editor is installed with version 1.3.8 or any prior version.

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
Upgrade available Upgrade to a release after 1.3.8
Interim mitigation

Update WECON PLC Editor to a version newer than 1.3.8. If immediate updating is not feasible, restrict network access to the editor and isolate affected systems from untrusted networks.

Fix this in Plc Editor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-25181 — 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-2020-25181 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