dbcve.org
Pfc200 FirmwareOperating system · Wago

CVE-2018-5459

CRITICAL · 9.8 CVSS v3.0 Published 2018-02-13
Fix available
A fix is available. Upgrade to 02.07.07 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
An Improper Authentication issue was discovered in WAGO PFC200 Series 3S CoDeSys Runtime versions 2.3.X and 2.4.X. An attacker can execute different unauthenticated remote operations because of the CoDeSys Runtime application, which is available via network by default on Port 2455. An attacker could execute some unauthenticated commands such as reading, writing, or deleting arbitrary files, or manipulate the PLC application during runtime by sending specially-crafted TCP packets to Port 2455.

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

Improper authentication in WAGO PFC200 Series CoDeSys Runtime (versions 2.3.X and 2.4.X) allows unauthenticated attackers to send specially-crafted TCP packets to Port 2455, enabling arbitrary file operations (read/write/delete) and runtime PLC application manipulation without any credentials.

MitigationIsolate the device on a restricted network segment and block Port 2455 at the firewall; if remote access is required, implement VPN with strong authentication; apply vendor firmware updates when available and disable CoDeSys Runtime network exposure if not needed.

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
Pfc200 FirmwareOperating system
Affected:< 02.07.07\(10\)

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.0/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 WAGO PFC200 hardware
    Locate the device model label or check the device's web interface/system information to confirm it is a WAGO PFC200 Series controller.
    Affected if The device is a WAGO PFC200 Series controller.
  2. Check CoDeSys Runtime version
    Access the device's web interface, check the runtime information page, or query the device to determine the CoDeSys Runtime version (2.3.X or 2.4.X).
    Affected if CoDeSys Runtime version 2.3.X or 2.4.X is installed.
  3. Verify firmware version
    Check the device firmware version through the web interface, boot menu, or by querying the device. Compare the installed version against 02.07.07(10).
    Affected if Firmware version is less than 02.07.07(10).
  4. Confirm Port 2455 exposure
    Perform a network scan or use a port scanner to check if TCP Port 2455 is open and listening on the device IP address.
    Affected if Port 2455 is open and reachable on the device.
  5. Assess network accessibility
    Determine if Port 2455 is accessible from untrusted network segments by reviewing firewall rules, network segmentation, and ACLs protecting the device.
    Affected if Port 2455 is accessible from network segments outside the trusted control network.

A user is affected if they have a WAGO PFC200 device with CoDeSys Runtime 2.3.X or 2.4.X, firmware below 02.07.07(10), and Port 2455 is open and accessible on their network.

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 02.07.07 or later
Fixed in 02.07.07
Interim mitigation

Isolate the device on a restricted network segment and block Port 2455 at the firewall; if remote access is required, implement VPN with strong authentication; apply vendor firmware updates when available and disable CoDeSys Runtime network exposure if not needed.

Recommended fix High confidence

PFC200 Firmware 02.07.07(10) or later

  1. Confirm current firmware version on the WAGO PFC200 device by accessing the web-based administration interface or using WAGO's management tools
  2. Download firmware version 02.07.07(10) or later from WAGO's official support website (www.wago.com) or contact WAGO technical support
  3. Review WAGO firmware upgrade documentation specific to PFC200 series for prerequisites and precautions
  4. Backup the current PLC project and configuration files to preserve application data
  5. Establish a stable power connection to the device during the firmware upgrade process
  6. Access the device's firmware update interface through the web management or appropriate tool
  7. Upload and install the firmware version 02.07.07(10) or newer
  8. Verify the firmware upgrade was successful by confirming the new version in the device interface
Caveat Review WAGO release notes for the 02.07.07 firmware to check for any configuration or feature changes that may require PLC program adjustments

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

Fix this in Pfc200 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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