WAGO: Multiple products vulnerable to local file inclusion
On affected Wago products an remote attacker with administrative privileges can access files to which he has already access to through an undocumented local file inclusion. This access is logged in a different log file than expected.
- Published
- Oct 17, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 39th percentile
- CWE
- CWE-610
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
10
Monitor
Low priority for now.
- CVSS
- 10 / 40 · 2.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · CERTVDE
- 2.7
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| wago | compact controller 100 firmware | cpe:2.3:o:wago:compact_controller_100_firmware |
| wago | compact controller 100 | cpe:2.3:h:wago:compact_controller_100 |
| wago | edge controller firmware | cpe:2.3:o:wago:edge_controller_firmware |
| wago | edge controller | cpe:2.3:h:wago:edge_controller |
| wago | pfc100 firmware | cpe:2.3:o:wago:pfc100_firmware |
| wago | pfc100 | cpe:2.3:h:wago:pfc100 |
| wago | pfc200 firmware | cpe:2.3:o:wago:pfc200_firmware |
| wago | pfc200 | cpe:2.3:h:wago:pfc200 |
| wago | touch panel 600 advanced firmware | cpe:2.3:o:wago:touch_panel_600_advanced_firmware |
| wago | touch panel 600 advanced | cpe:2.3:h:wago:touch_panel_600_advanced |
| wago | touch panel 600 marine firmware | cpe:2.3:o:wago:touch_panel_600_marine_firmware |
| wago | touch panel 600 marine | cpe:2.3:h:wago:touch_panel_600_marine |
and 2 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- wago compact controller 100 firmware19 and later · up to 26 inclusive
- wago edge controller firmware18 and later · up to 26 inclusive
- wago pfc100 firmware16 and later · up to 26 inclusive
- wago pfc200 firmware16 and later · up to 26 inclusive
- wago touch panel 600 advanced firmware16 and later · up to 26 inclusive
- wago touch panel 600 marine firmware16 and later · up to 26 inclusive
- wago touch panel 600 standard firmware16 and later · up to 26 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (CERTVDE). Independent of NVD's CPE analysis and usually ahead of it.
WAGO Compact Controller CC100
- FW19 and later · up to and including FW26affected · semver
WAGO Edge Controller
- FW18 and later · up to and including FW26affected · semver
WAGO PFC100
- FW16 and later · up to and including FW26affected · semver
WAGO PFC200
- FW16 and later · up to and including FW26affected · semver
WAGO Touch Panel 600 Advanced Line
- FW16 and later · up to and including FW26affected · semver
WAGO Touch Panel 600 Marine Line
- FW16 and later · up to and including FW26affected · semver
WAGO Touch Panel 600 Standard Line
- FW16 and later · up to and including FW26affected · semver
Same product
wago: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-1698WAGO: WBM Command Injection in multiple products64This week
- CVE-2023-3379WAGO: Improper Privilege Management in web-based management21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Floris Hendriks and Jeroen WijenberghRadboud Universityreporter
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-610 · Externally Controlled Reference to a Resource in Another SphereCVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.