Two operators at a control-room desk with a row of monitors, a laptop and keyboards

OT/ICS security

WAGO PFC100, PFC200, CC100 and Touch Panel 600 vulnerabilities: CVEs, fixed firmware and hardening

Last updated:

WAGO PFC100, PFC200, Compact Controller CC100 and Touch Panel 600 devices are Linux controllers whose most serious CVEs sit in three places: the web-based management (WBM), the I/O-Check commissioning service on port 6626, and the CODESYS 2.3 or CODESYS V3 runtime that WAGO ships in its firmware. CERT@VDE scores several of these at 9.8, and for CVE-2019-5080 in I/O-Check WAGO lists every firmware version as affected, with disabling port 6626 as the only measure. Securing these controllers means running WAGO's fixed firmware for your hardware generation, switching off I/O-Check, unused runtime ports and WBM where possible, changing default passwords, and keeping the devices off untrusted networks.

Key takeaways

  • A WAGO PFC controller exposes several services, and each one has its own CVE history.
  • I/O-Check accepts unauthenticated packets that can change settings, delete the application, reset the device and run code.
  • The unauthenticated ones, because WBM is the controller's administration interface.
  • WAGO controllers run CODESYS, so CODESYS advisories reach them, but the fix always arrives as WAGO firmware.

How are WAGO PFC controllers reached on the network?

A WAGO PFC controller exposes several services, and each one has its own CVE history. WAGO publishes product security advisories through CERT@VDE; its PSIRT page points users to the CERT@VDE WAGO advisory list and its RSS feed. Read across those advisories, the services you need to inventory are:

Service What it does What WAGO's advisories say
Web-based management (WBM) Browser UI for administration, commissioning and updates; PHP-based configuration backend VDE-2020-015 calls WBM "typically used for administration, commissioning and updates"; VDE-2022-060 says it can be deactivated from the command line if not needed
I/O-Check (iocheckd), port 6626 Commissioning and diagnostics service used by WAGO tools "Only needed during installation and commissioning, not during normal operations"; WAGO recommends disabling port 6626 afterwards (VDE-2019-022, VDE-2025-080)
CODESYS 2.3 runtime, port 2455 PLC programming and online access for WAGO-I/O-PRO projects VDE-2021-014 and VDE-2021-049 say to disable the CODESYS 2.3 port 2455; CISA's ICSA-18-044-01 says it is available on the network by default
CODESYS V3 runtime (e!RUNTIME) PLC programming and online access for e!COCKPIT projects, plus web visualisation and OPC UA VDE-2023-026 recommends WBM "port authentication" and deactivating the CODESYS programming port when not commissioning
SSH Shell access to the Linux system VDE-2024-014 lists PFC100, PFC200, CC100, Edge Controller and Touch Panel 600 firmware as affected by Terrapin
Optional services OpenVPN, BACnet/IP and others VDE-2024-008 (OpenVPN in WBM) and VDE-2025-102 (BACnet IP stack)

The product families map to WAGO article numbers that every advisory uses: PFC100 is 750-81xx (750-810x for the first generation, 750-811x for G2), PFC200 is 750-82xx (750-820x G1, 750-821x G2), CC100 is 751-9301 and 751-9401, Touch Panel 600 is 762-4xxx (Standard Line), 762-5xxx (Advanced Line) and 762-6xxx (Marine Line), and the Edge Controller is 752-8303/8000-0002.

Why is the I/O-Check service the first thing to switch off?

I/O-Check accepts unauthenticated packets that can change settings, delete the application, reset the device and run code. In VDE-2019-022, WAGO summarizes the Cisco Talos findings as allowing "a remote attacker to change the setting, delete the application, set the device to factory defaults, code execution and to cause a system crash or denial of service". Talos reported stack and heap buffer overflows in iocheckd, such as CVE-2019-5074 in TALOS-2019-0863, and NVD scores CVE-2019-5074 and CVE-2019-5082 at 9.8 (CVSS v3.1). CISA republished the set as ICSA-20-065-01 and scored several of them 10.0.

The service kept producing advisories after that:

  • FW15 fixes for the 2019 set. VDE-2019-022 says CVE-2019-5073, 5074, 5075, 5079, 5081 and 5082 are fixed in firmware FW15 or later, and that disabling port 6626 after commissioning is "the easiest and securest way" to protect the device.
  • CVE-2020-12522, command injection. VDE-2020-045 covers PFC100, PFC200 and Touch Panel 600 up to FW10; NVD scores it 9.8 and WAGO says it was fixed in FW11, released in December 2017.
  • Authenticated follow-ups. VDE-2020-011 lists 20 more iocheckd flaws (CVE-2019-5166 to CVE-2019-5186, CERT@VDE up to 7.8) that need a login able to write files, with FW16 as the first unaffected firmware. VDE-2020-036 adds CVE-2021-34566 to CVE-2021-34569 (CERT@VDE up to 9.8) for firmware up to FW18 Patch 2, with "Disable I/O-Check service" as the mitigation.
  • CVE-2019-5080, no fixed version. VDE-2025-080 (9 September 2025) says one unauthenticated packet can cause a denial of service and "weaken credentials resulting in the default documented credentials being applied to the device". It lists all firmware versions of PFC100, PFC200, CC100, Touch Panel 600, the Edge Controller and many 750 controllers as affected, scores the flaw 9.1 (CVSS v3.1, matching NVD), and gives one measure: disable port 6626 after commissioning.

That last advisory changes the picture CISA gave in 2020. ICSA-20-065-01 listed FW15 as the fix for CVE-2019-5080 along with the rest of the set; WAGO's 2025 advisory does not name a fixed firmware. Treat a reachable port 6626 as a finding on every WAGO controller, whatever its firmware.

Which web-based management CVEs matter most?

The unauthenticated ones, because WBM is the controller's administration interface. WAGO's advisories describe four kinds of WBM flaws on PFC100, PFC200, CC100 and Touch Panel 600:

CVE What it allows (per WAGO / CERT@VDE) Affected Score Fix in WAGO's advisory
CVE-2022-45138, CVE-2022-45140 Configuration backend usable without authentication; 45140 lets an unauthenticated user "write arbitrary data with root privileges to the storage" PFC100, PFC200, CC100, TP600, Edge Controller FW16 to FW23 CERT@VDE 9.8 each FW22 Patch 1, or FW24 or higher (VDE-2022-060)
CVE-2023-1698 Command injection in the "legal information" plugin; run commands as the www user, create users, take over the system PFC100 FW22, PFC200 FW20 to FW23 (FW23 only on 750-821x), CC100 FW22 and FW23, TP600 CERT@VDE 9.8 FW22 SP1; FW24 for 750-821x and CC100 (VDE-2023-007)
CVE-2022-3738 Unauthenticated download of a backup file that may contain credentials and keys, if a user created one since the last reboot Same families, FW16 to FW22 CERT@VDE and NVD 5.9 FW22 Patch 1 (VDE-2022-054)
CVE-2019-5134, CVE-2019-5135 Timing side channel that lets an attacker reconstruct WBM password hashes PFC100, PFC200, TP600 FW05 to FW14 NVD 7.5 (5134) Affected range ends at FW14 (VDE-2020-006)
CVE-2020-6090 Admin-level WBM user installs packages with root privileges PFC100, PFC200, TP600 before 03.04.10 (FW16) NVD v3.1 7.2; CERT@VDE v3.0 9.1 Documentation corrected from FW16; strong admin passwords (VDE-2020-015)
CVE-2023-3379 A specific WBM user can reset passwords of other non-root users PFC100, PFC200 to FW22 Patch 1; CC100, TP600 to FW25 CERT@VDE 5.3 FW22 Patch 2; FW26 for 750-821x, CC100, TP600 (VDE-2023-015)
CVE-2024-1490 Admin with OpenVPN enabled runs shell commands G2, CC100, TP600 up to wago_os_linux 4.5.10; G1 up to 3.10.10 CERT@VDE 7.2; NVD Awaiting Analysis Drop OpenVPN privileges per WAGO's Cyber Security for Controller manual, section 7.1.4 (VDE-2024-008)

Two points stand out. CVE-2023-1698 is the WAGO CVE with the highest exploitation-probability score: FIRST EPSS rates it 0.8191 on 2026-11-19. And CVE-2020-6090 is a design point more than a bug: WAGO says installing software through WBM "is an intended functionality", so the admin password is effectively a root password. The PHP runtime under WBM is the newest exposure, covered in the KEV section below.

Which CODESYS runtime CVEs reach WAGO firmware?

WAGO controllers run CODESYS, so CODESYS advisories reach them, but the fix always arrives as WAGO firmware. WAGO publishes its own CERT@VDE advisory with WAGO firmware versions for each relevant CODESYS advisory. The CODESYS runtime guide covers the CODESYS side in depth; this is the WAGO view.

CODESYS 2.3 (WAGO-I/O-PRO), port 2455. CISA's ICSA-18-044-01 described CVE-2018-5459 on PFC200 controllers: the CODESYS runtime "is available via network by default on Port 2455", and unauthenticated TCP packets to it could read, write or delete files and manipulate the running PLC application (NVD v3.0 9.8, fixed with FW11 per CISA). Later WAGO advisories kept the same advice:

  • VDE-2021-014 brings CODESYS V2 runtime and web server flaws such as CVE-2021-30188 (NVD 9.8) to PFC200 750-82xx firmware before 03.06.19 (18), and tells users to "disable the CODESYS 2.3 Web-Visualisation and CODESYS 2.3 port 2455".
  • VDE-2022-040 adds CODESYS Advisories 2022-11 to 2022-13 for PFC200 firmware up to 03.10.08 (22). Its interim measures are online user management, strong passwords, moving to e!RUNTIME or CODESYS V3, and "switching off the CODESYS IP port 2455 after commissioning".
  • VDE-2023-006 (CVE-2023-1619 and CVE-2023-1620, CERT@VDE 4.9) is fixed for the PFC200 family in FW22 Patch 2. It also names the WBM switch: Configuration > PLC Runtime Services > CODESYS 2 > communication enabled.

CODESYS V3 (e!RUNTIME). These advisories cover PFC100, PFC200, CC100, Edge Controller and Touch Panel 600:

WAGO advisory CODESYS CVEs WAGO firmware affected WAGO fix or measure
VDE-2022-031 CVE-2019-9013 (credentials sent without TLS, CERT@VDE 8.8), CVE-2020-12069 and others Up to 03.06.19 (18) CODESYS general defense measures
VDE-2022-035 CVE-2021-33485 (heap overflow, CERT@VDE 9.8), CVE-2021-36763 and others PFC up to 03.09.05 (21) 03.10.08 (22) for PFC100 and PFC200; 03.10.09 (22) for TP600 and CC100
VDE-2023-026 CVE-2022-47378 to CVE-2022-47393, including CVE-2022-47390 (CERT@VDE 8.8) and CVE-2022-47378 Up to FW25 Activate WBM port authentication, change the default admin password, deactivate the programming port
VDE-2025-008 CVE-2023-6357 (OS command injection via file system libraries, CERT@VDE 8.8) G1 before 03.10.11 (FW22 Patch 2); G2, CC100, TP600 before 04.05.10 (FW27) FW22 Patch 2 or FW27; change the standard WBM password
VDE-2025-081 CVE-2025-41738 (unauthenticated visualisation server DoS, CERT@VDE 7.5), CVE-2025-41739, CVE-2025-41700 CC100, PFC100 G2, PFC200 G2, TP600 before 4.10.0 (FW32) Firmware 4.10.0 (FW32) or higher

The engineering tool is part of the attack surface too: VDE-2023-068 lists e!COCKPIT up to 1.11.2.0 as affected by CODESYS Development System flaws, alongside the runtime CVEs. If the controller also exposes OPC UA from the CODESYS stack, WAGO's VDE-2025-009 (CVE-2024-5000) applies; see the OPC UA security guide. For TwinCAT-based controllers with a similar layered runtime, compare the Beckhoff ADS guide.

Are WAGO controller CVEs exploited in the wild?

No CISA KEV entry names WAGO or CODESYS as the vendor as of 2026-11-20. The CISA KEV data (catalog version 2026.11.18, 1,786 entries) has none. The exploited flaws that do reach WAGO controllers come through the Linux platform underneath, and WAGO has said so in its own advisories:

KEV entry (date added) Component WAGO advisory WAGO fix
CVE-2026-109618 and CVE-2026-109619, "PHP2Shell" (2026-10-26) PHP runtime behind WBM VDE-2026-132, 18 November 2026 Firmware 4.10.4 (FW32) or later; IPK security patches for FW31 (4.9.1), firmware below 4.4.1 and below 3.10.10; until then, disable the web server in the security settings
CVE-2025-32463, sudo --chroot (2025-09-29) sudo VDE-2025-082 Firmware 04.08.01 (FW30) or later; IPK updating sudo to 1.9.17p1
CVE-2022-0847, Dirty Pipe (2022-04-25) Linux kernel VDE-2022-009 03.09.04 (21) for PFC100, PFC200 and CC100; 03.07.19 (19) for TP600

VDE-2026-132 lists PFC100 G1 and G2, PFC200 G1 and G2, CC100, Touch Panel 600, the Edge Controller, PFC300 and WP400 as affected. NVD scores CVE-2026-109618 at 9.8 and CVE-2026-109619 at 8.1 (CVSS v3.1), and FIRST EPSS on 2026-11-19 puts both at 0.99999. The sudo and Dirty Pipe flaws are local privilege escalations; on a WAGO controller they turn any low-privileged foothold, such as a WBM command injection running as www, into root. The Linux kernel CVE guide explains why kernel flaws persist in device firmware.

Among WAGO's own CVEs, FIRST EPSS scores dated 2026-11-19 rank CVE-2023-1698 far ahead at 0.8191, followed by the 2019 iocheckd flaws CVE-2019-5082 (0.0332) and CVE-2019-5074 (0.0328), CVE-2020-12522 (0.0305) and CVE-2018-5459 (0.0268). Terrapin, CVE-2023-48795, which WAGO's VDE-2024-014 fixes in FW22 Patch 2 and FW27, scores 0.9355. Rank by reachability first, as the KEV and EPSS prioritization guide explains: an unauthenticated WBM or port 6626 flaw on a controller any host can reach comes before an authenticated runtime CVE behind port authentication.

How do you find the firmware version to compare?

WAGO's advisories use two notations for the same firmware, so the inventory needs the full version string and the hardware generation:

Notation Example in WAGO advisories Used for
FW release number FW22 Patch 2, FW27, FW30, FW32 Most advisories, both generations
Full version (FW) 03.10.08 (22), 03.10.11 (FW22 Patch 2), 04.05.10 (FW27), 04.08.01 (FW30), 4.10.4 (FW32) Newer advisories and CSAF
wago_os_linux version wago_os_linux 4.5.10, <4.10.0 CERT@VDE CSAF product names
Custom firmware 04.06.01 (70), <4.10.0 (70) Customer-specific builds; WAGO points to its support for the latest version

A practical sequence:

  1. Record article numbers, not product namesA "PFC200" can be a 750-820x (G1) on the 03.x line or a 750-821x (G2) on the 04.x line, and many advisories give them different fixes, as VDE-2023-007 and VDE-2023-015 do.
  2. Read the full version stringOne FW number can cover several builds in WAGO's advisories: FW30 appears as 04.08.01 in VDE-2025-082 and as 4.8.9 in VDE-2025-102, and FW32 as 4.10.0 in VDE-2025-081 and 4.10.4 in VDE-2026-132. Compare against the exact version each advisory names.
  3. Check G1 devices separatelyThe first-generation 750-810x and 750-820x stay on the 03.10 line; VDE-2025-062 and VDE-2025-008 fix them in 03.10.11 (FW22 Patch 2), while G2 devices move to 04.x releases.
  4. Include e!COCKPIT and WAGO-I/O-PRO installationsEngineering PCs carry their own CVEs (VDE-2023-068, VDE-2022-040).
  5. Do not rely on CPE matching aloneMany WAGO CVE records cover CODESYS or PHP components, so a scanner keyed on the WAGO product name can miss them; the patch management guide for IEC 62443-2-3 covers tracking vendor-qualified patches.

How should WAGO PFC controllers be hardened?

Treat every WAGO controller as a Linux server with PLC duties. The measures below come from WAGO's own advisories, which also point to WAGO's "Cyber Security for Controller PFC100 / PFC200" manual and the BSI ICS Security Compendium:

  1. Disable I/O-Check (port 6626) after commissioningWAGO calls it the easiest and most secure protection for the iocheckd CVEs, and for CVE-2019-5080 it is the only one.
  2. Turn off the runtime ports you do not useFor CODESYS 2.3, switch off CODESYS 2 communication in WBM, disable the 2.3 web visualisation and close port 2455. For CODESYS V3, activate port authentication in WBM so that none of the CODESYS Advisory 2023-02 flaws can be exploited by unauthenticated users (VDE-2023-026), and deactivate the programming port outside commissioning.
  3. Change default passwordsWAGO's mitigations for VDE-2023-026 and VDE-2025-008 include changing the default or standard admin password; CVE-2019-5080 resets a device to its documented defaults, which is one more reason to keep 6626 closed.
  4. Reduce WBM exposureDeactivate WBM from the command line where it is not needed (VDE-2022-060), or disable the web server in the security settings while waiting for the PHP2Shell fix (VDE-2026-132). Where WBM stays on, restrict it to named administrator hosts.
  5. Update to WAGO's fixed firmware for the right generationAs of 2026-11-20, the newest fixes in the advisories above are 4.10.0 or 4.10.4 (FW32) for G2, CC100 and TP600, and IPK security patches for firmware below 3.10.10 on G1. WAGO's Remediation sections name IPK patches from the WAGO Download Center as interim fixes for sudo and PHP.
  6. Drop OpenVPN privileges and remove unused optional servicesVDE-2024-008 points to section 7.1.4 of the Cyber Security for Controller manual for OpenVPN; VDE-2025-102 shows that a BACnet/IP stack enabled on a G2 controller adds an unauthenticated file read and write path (CVE-2025-41753, CERT@VDE 9.8), fixed in 4.8.9 (FW30).
  7. Segment and never expose controllers to the internetWAGO's advisories repeat "Do not directly connect the device to the internet" and "Restrict network access to the device". Zone controllers following the Purdue model and the NIST SP 800-82 OT security guide, and allow WBM, SSH, 2455, the CODESYS V3 port and 6626 only from named engineering hosts.

If the controller serves field protocols, the Modbus guide and the BACnet guide cover their protocol-level weaknesses. For SSH components in firmware, see the OpenSSH firmware guide.

How do you monitor WAGO controllers on a plant network?

Start with a baseline of who talks to each controller and on which ports. Useful flow-level signals:

  • Any traffic to port 6626 outside a commissioning window, since I/O-Check should be off in operation.
  • New hosts opening TCP 2455 or the CODESYS V3 programming port, especially from outside the engineering zone.
  • WBM sessions from hosts other than named administrators, given CVE-2023-1698, CVE-2022-45138 and the PHP2Shell flaws.
  • SSH sessions to controllers from outside the engineering zone or from the internet.
  • A controller suddenly accepting a login with default credentials after a burst of traffic on 6626, the behaviour described for CVE-2019-5080.

Flow records show who connected to which port and when; seeing which CODESYS service or I/O-Check command a session carried needs a protocol decoder. Map alerts to MITRE ATT&CK for ICS techniques such as Program Download and Modify Parameter.

Worked example: what does a review of one building automation panel find?

Synthetic example, not a real site. A panel has two PFC200 controllers, one 750-8202 (G1) and one 750-8212 (G2), a CC100 for a ventilation unit and a Touch Panel 600 as the local HMI.

Observation Why it matters Action
Port 6626 open on all four devices CVE-2019-5080 affects all firmware versions and resets credentials to defaults Disable I/O-Check on every device after commissioning
750-8212 and CC100 on FW26 Below FW27 for CVE-2023-6357 and Terrapin, below FW32 for PHP2Shell Update to FW32 (4.10.4 per VDE-2026-132), or install the IPK patches as an interim
750-8202 on 03.10.08 (22) Below 03.10.11 (FW22 Patch 2) for CVE-2023-6357 and CVE-2023-3379 Update to FW22 Patch 2 and install WAGO's PHP IPK patch for firmware below 3.10.10
CODESYS 2.3 port 2455 open on the G1 PFC200, which runs an e!RUNTIME project Unused runtime port with a long CVE history Switch off CODESYS 2 communication in WBM
WBM reachable from the building office VLAN Unauthenticated WBM CVEs and PHP2Shell are web-facing Restrict WBM to the facility engineer's laptop, or disable it where not needed
Default admin password unchanged on the CC100 Authenticated CODESYS V3 CVEs become reachable to anyone who knows the default Change it and enable WBM port authentication

Where does passive monitoring fit in a WAGO review?

A passive capture shows who talks to the controllers without sending a packet to them, which matters for a service like I/O-Check that a single crafted packet can crash. SoftWSP's OT Snapshot reads Zeek and ICSNPP logs from a mirror-port recording and builds a host-by-port inventory, including hosts using port 6626, TCP 2455, web and SSH ports, and lists remote-access sessions (SSH, Telnet, RDP, VNC) that cross from outside the private address range. It has no I/O-Check or CODESYS decoder, so this traffic shows at connection level only, without commands. For a controller list with article numbers and firmware versions, Device & Firmware Security identifies components and versions and matches them against NVD, CISA KEV, FIRST EPSS and CISA ICS advisories. An engineer reviews every AI-drafted, cited report before it is sent.

What are the common pitfalls?

  • Leaving I/O-Check on after commissioning, which keeps CVE-2019-5080 reachable on every firmware version.
  • Matching "PFC200" instead of the article number, then applying a G2 firmware fix to a G1 device or the reverse.
  • Comparing FW numbers only, when one FW release appears with several build versions across WAGO's advisories.
  • Treating the WBM admin password as a web password; WAGO says software installation through WBM runs with root privileges.
  • Patching WAGO's own CVEs and missing the PHP, sudo and kernel advisories, which are the ones in CISA KEV.
  • Leaving CODESYS 2.3 port 2455 open on controllers that run an e!RUNTIME project.

This guide draws on WAGO advisories published through CERT@VDE (VDE-2019-022, VDE-2020-006, VDE-2020-011, VDE-2020-015, VDE-2020-036, VDE-2020-045, VDE-2021-014, VDE-2021-049, VDE-2022-009, VDE-2022-031, VDE-2022-035, VDE-2022-040, VDE-2022-054, VDE-2022-060, VDE-2023-006, VDE-2023-007, VDE-2023-015, VDE-2023-026, VDE-2023-068, VDE-2024-008, VDE-2024-014, VDE-2025-008, VDE-2025-009, VDE-2025-062, VDE-2025-080, VDE-2025-081, VDE-2025-082, VDE-2025-102 and VDE-2026-132); WAGO's PSIRT page; CISA ICS advisories ICSA-18-044-01, ICSA-20-065-01 and ICSA-23-325-01; Cisco Talos report TALOS-2019-0863; and NVD records. KEV and EPSS facts are as of 2026-11-20. It is general information, not a substitute for WAGO's product-specific advisories or a check of your exact article number and firmware version.

Put this guide to work

Frequently asked questions

What is the WAGO I/O-Check service and why should port 6626 be closed?

I/O-Check is a WAGO commissioning service that the iocheckd daemon serves on IP port 6626. WAGO's advisories VDE-2019-022 and VDE-2025-080 say the protocol is only needed during installation and commissioning and that it is highly recommended to disable port 6626 afterwards. Cisco Talos found unauthenticated buffer overflows in iocheckd in 2019 (CVE-2019-5074, CVE-2019-5082 and others, NVD 9.8, fixed in FW15). In September 2025 WAGO published VDE-2025-080 for CVE-2019-5080: one unauthenticated packet causes a denial of service and resets the device to its documented default credentials. That advisory lists all firmware versions of PFC100, PFC200, CC100, Touch Panel 600 and many 750 controllers as affected, and its only measure is to disable port 6626.

Which WAGO firmware fixes the unauthenticated web-based management flaws?

For CVE-2022-45138 and CVE-2022-45140 (CERT@VDE 9.8), where the configuration backend of web-based management accepted unauthenticated reads, writes and root-level storage writes, WAGO's VDE-2022-060 recommends FW22 Patch 1 or FW24 or higher. For CVE-2023-1698 (CERT@VDE 9.8), command injection in the legal-information plugin, VDE-2023-007 names FW22 SP1 for PFC100, PFC200 (750-82xx) and Touch Panel 600, and FW24 for the PFC200 750-821x and CC100. Touch Panel 600 can also use FW24. Older firmware lines need a newer release for later issues, such as FW26 for the CVE-2023-3379 password-reset flaw.

Are WAGO PLC vulnerabilities in the CISA KEV catalog?

No KEV entry names WAGO or CODESYS as the vendor as of 2026-11-20 (catalog version 2026.11.18, 1,786 entries). Three KEV entries do reach WAGO firmware through third-party components, according to WAGO's own advisories: the PHP2Shell flaws CVE-2026-109618 and CVE-2026-109619 (added 2026-10-26, WAGO VDE-2026-132), the sudo flaw CVE-2025-32463 (added 2025-09-29, WAGO VDE-2025-082) and Dirty Pipe, CVE-2022-0847 (added 2022-04-25, WAGO VDE-2022-009). FIRST EPSS on 2026-11-19 scores CVE-2023-1698, the WAGO web-based management command injection, at 0.8191.

Which WAGO controllers use CODESYS 2.3 and which use CODESYS V3?

WAGO's advisories split the runtime families. The CODESYS 2.3 runtime, programmed with WAGO-I/O-PRO, appears in advisories for the PFC200 750-82xx models and the older 750-8xx Ethernet controllers, and uses port 2455. The CODESYS V3 runtime, which WAGO calls e!RUNTIME and programs with e!COCKPIT, appears in advisories for PFC100, PFC200, CC100, Edge Controller and Touch Panel 600. CODESYS V3 CVEs such as CVE-2022-47390 therefore reach WAGO devices through WAGO firmware releases, and WAGO publishes its own CERT@VDE advisory with WAGO firmware versions for each CODESYS advisory.

How do I disable unused services on a WAGO PFC200?

WAGO's advisories name the switches. Disable I/O-Check and port 6626 after commissioning. For CODESYS 2.3, turn off Configuration > PLC Runtime Services > CODESYS 2 > communication enabled, as VDE-2023-006 describes, and disable the CODESYS 2.3 web visualisation. For CODESYS V3, activate port authentication in web-based management and deactivate the programming port when no one is commissioning. If web-based management is not needed, VDE-2022-060 says it can be deactivated from the command line, and VDE-2026-132 says the web server can be disabled in the security settings. Change the default admin password in every case.

Sources

  1. CERT@VDE: WAGO advisory list
  2. WAGO: Security Instructions, PSIRT at WAGO
  3. CERT@VDE VDE-2019-022: WAGO multiple vulnerabilities in I/O-Check service in multiple devices (CVE-2019-5073 to CVE-2019-5082)
  4. CERT@VDE VDE-2020-011: WAGO multiple vulnerabilities in I/O-Check service (CVE-2019-5166 to CVE-2019-5186)
  5. CERT@VDE VDE-2020-045: WAGO command injection in I/O-Check service (CVE-2020-12522)
  6. CERT@VDE VDE-2020-036: WAGO multiple vulnerabilities in I/O-Check service (CVE-2021-34566 to CVE-2021-34569)
  7. CERT@VDE VDE-2025-080: WAGO multiple vulnerabilities in I/O-Check service (CVE-2019-5080)
  8. CERT@VDE VDE-2020-006: WAGO web-based management authentication vulnerabilities (CVE-2019-5134, CVE-2019-5135)
  9. CERT@VDE VDE-2020-015: WAGO web-based management code execution (CVE-2020-6090)
  10. CERT@VDE VDE-2022-054: WAGO unauthenticated configuration export in web-based management (CVE-2022-3738)
  11. CERT@VDE VDE-2022-060: WAGO multiple vulnerabilities in web-based management (CVE-2022-45137 to CVE-2022-45140)
  12. CERT@VDE VDE-2023-007: WAGO unauthenticated command execution via web-based management, Update A (CVE-2023-1698)
  13. CERT@VDE VDE-2023-015: WAGO improper privilege management in web-based management (CVE-2023-3379)
  14. CERT@VDE VDE-2024-008: WAGO vulnerability in WBM through OpenVPN (CVE-2024-1490)
  15. CERT@VDE VDE-2026-132: WAGO multiple devices affected by PHP2Shell (CVE-2026-109618, CVE-2026-109619)
  16. CERT@VDE VDE-2021-014: WAGO multiple vulnerabilities in CODESYS Runtime 2.3
  17. CERT@VDE VDE-2022-040: WAGO controllers with WAGO I/O-Pro / CODESYS 2.3 runtime
  18. CERT@VDE VDE-2023-006: WAGO controller with CODESYS 2.3 runtime denial of service (CVE-2023-1619, CVE-2023-1620)
  19. CERT@VDE VDE-2022-035: WAGO product series affected by multiple CODESYS vulnerabilities (CVE-2021-33485 and others)
  20. CERT@VDE VDE-2023-026: WAGO products with vulnerabilities in e!Runtime / CODESYS V3 runtime (CVE-2022-47378 to CVE-2022-47393)
  21. CERT@VDE VDE-2025-008: WAGO vulnerabilities in CODESYS Control (CVE-2023-6357)
  22. CERT@VDE VDE-2025-081: WAGO PLCs and communication components affected by CODESYS Control vulnerabilities (CVE-2025-41700, CVE-2025-41738, CVE-2025-41739)
  23. CERT@VDE VDE-2025-102: WAGO devices affected by a vulnerability in the BACnet IP stack (CVE-2025-41753)
  24. CERT@VDE VDE-2024-014: WAGO multiple products affected by Terrapin (CVE-2023-48795)
  25. CERT@VDE VDE-2025-082: WAGO critical sudo vulnerability in multiple products (CVE-2025-32463)
  26. CERT@VDE VDE-2022-009: WAGO multiple products affected by Linux kernel vulnerability Dirty Pipe (CVE-2022-0847)
  27. CISA CSAF: ICSA-20-065-01 WAGO I/O-CHECK
  28. CISA CSAF: ICSA-18-044-01 WAGO PFC200 Series (CVE-2018-5459)
  29. CISA CSAF: ICSA-23-325-01 WAGO PFC200 Series (CVE-2023-4089)
  30. Cisco Talos: TALOS-2019-0863, WAGO PFC200 iocheckd service I/O-Check stack buffer overflow (CVE-2019-5074)
  31. NVD: CVE-2023-1698 (WAGO web-based management command injection)
  32. NVD: CVE-2019-5074 (WAGO iocheckd stack buffer overflow)
  33. NVD: CVE-2018-5459 (WAGO PFC200 CODESYS runtime on port 2455)
  34. NVD: CVE-2020-6090 (WAGO web-based management code execution)
  35. CISA Known Exploited Vulnerabilities catalog (data mirror on GitHub)
  36. FIRST: Exploit Prediction Scoring System (EPSS)
Was this guide helpful?

In this cluster

WAGO PFC100, PFC200, CC100 and Touch Panel 600 vulnerabilities: CVEs, fixed firmware and hardening