dbcve.org
PlcwinntApplication · Codesys

CVE-2022-31806

CRITICAL · 9.8 CVSS v3.1 Published 2022-06-24
Fix available
A fix is available. Upgrade to 2.4.7.57 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
In CODESYS V2 PLCWinNT and Runtime Toolkit 32 in versions prior to V2.4.7.57 password protection is not enabled by default and there is no information or prompt to enable password protection at login in case no password is set at the controller.

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 · high confidence

The CODESYS V2 PLCWinNT and Runtime Toolkit 32 allow remote unauthenticated access because password protection is not enabled by default and users are not prompted to set a password during login. An attacker can connect to the PLC runtime without any credentials, potentially achieving full control over the industrial control system.

MitigationEnable password protection on the affected CODESYS controllers and upgrade to version V2.4.7.57 or later to remediate this vulnerability.

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
PlcwinntApplication
Affected:< 2.4.7.57
Runtime ToolkitApplication
Affected:< 2.4.7.57

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Identify installed CODESYS version
    Locate the CODESYS PLCWinNT or Runtime Toolkit 32 installation and retrieve its version information from the application, About dialog, or installed program details
    Affected if The installed version is earlier than 2.4.7.57 (e.g., 2.4.x.y where y < 57, or any 2.3.x or earlier release)
  2. Verify password protection status
    Access the CODESYS runtime configuration or control panel and examine the security settings for the PLC runtime to determine whether password protection is enabled for remote connections
    Affected if Password protection is disabled or not configured on the PLC runtime
  3. Test for unauthenticated remote access
    Attempt to establish a remote connection to the PLC runtime using CODESYS or a network tool without providing any credentials
    Affected if The connection succeeds without requiring authentication credentials
  4. Check runtime security configuration
    Inspect the CODESYS runtime configuration files or security settings for any indication that authentication enforcement is missing or set to 'none'
    Affected if The configuration shows no password requirement or uses default/open security settings

You are affected if your CODESYS PLCWinNT or Runtime Toolkit 32 version is below 2.4.7.57 AND password protection is not enabled, allowing remote unauthenticated access to the PLC runtime.

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.

dbcve · scoped
Upgrade available Upgrade to 2.4.7.57 or later
Fixed in 2.4.7.57
Interim mitigation

Enable password protection on the affected CODESYS controllers and upgrade to version V2.4.7.57 or later to remediate this vulnerability.

Recommended fix High confidence

CODESYS V2 PLCWinNT and Runtime Toolkit 32 version 2.4.7.57

  1. 1. Identify the currently installed version of CODESYS V2 PLCWinNT or Runtime Toolkit 32
  2. 2. Download version 2.4.7.57 or later from the official CODESYS download source (customers.codesys.com)
  3. 3. Create a backup of all existing PLC projects and configurations
  4. 4. Install the updated version following the standard CODESYS installation procedure
  5. 5. After upgrade, navigate to the controller security settings and verify password protection is enabled or configure an appropriate password
  6. 6. Test that the controller requires authentication before granting access

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Plcwinnt Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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