CVE-2021-21001: WAGO: PFC200 Access to files outside the home directory
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 67% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Severity is disputed: the assigning authority (CNA) scores it 9.1, NVD 6.5.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
On WAGO PFC200 devices in different firmware versions with special crafted packets an authorised attacker with network access to the device can access the file system with higher privileges.
- Published
- May 24, 2021
- Updated
- Jun 16, 2026
- EPSS
- 1.1% · 67th percentile
- CWE
- CWE-22
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
CNA vs NVD score
- NVD
- 6.5
- CNA · CERTVDE
- 9.1
- 2.6 point gap
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| wago | 750-823 firmware | cpe:2.3:o:wago:750-823_firmware |
| wago | 750-823 | cpe:2.3:h:wago:750-823 |
| wago | 750-829 firmware | cpe:2.3:o:wago:750-829_firmware |
| wago | 750-829 | cpe:2.3:h:wago:750-829 |
| wago | 750-831 firmware | cpe:2.3:o:wago:750-831_firmware |
| wago | 750-831 | cpe:2.3:h:wago:750-831 |
| wago | 750-832 firmware | cpe:2.3:o:wago:750-832_firmware |
| wago | 750-832 | cpe:2.3:h:wago:750-832 |
| wago | 750-852 firmware | cpe:2.3:o:wago:750-852_firmware |
| wago | 750-852 | cpe:2.3:h:wago:750-852 |
| wago | 750-862 firmware | cpe:2.3:o:wago:750-862_firmware |
| wago | 750-862 | cpe:2.3:h:wago:750-862 |
and 42 more
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 Series Ethernet Controller
- 750-8202/xxx-xxx and later · before 03.06.19 (18)affected
- 750-8203/xxx-xxx and later · before 03.06.19 (18)affected
- 750-8204/xxx-xxx and later · before 03.06.19 (18)affected
- 750-8206/xxx-xxx and later · before 03.06.19 (18)affected
- 750-8207/xxx-xxx and later · before 03.06.19 (18)affected
- 750-8208/xxx-xxx and later · before 03.06.19 (18)affected
- 750-8210/xxx-xxx and later · before 03.06.19 (18)affected
- 750-8211/xxx-xxx and later · before 03.06.19 (18)affected
- 750-8212/xxx-xxx and later · before 03.06.19 (18)affected
- 750-8213/xxx-xxx and later · before 03.06.19 (18)affected
WAGO Series PFC200 Controller
- 750-823 and later · up to and including FW07affected
- 750-829 and later · up to and including FW14affected
- 750-831/000-00x and later · up to and including FW14affected
- 750-832/000-00x and later · up to and including FW06affected
- 750-852 and later · up to and including FW14affected
- 750-862 and later · up to and including FW07affected
- 750-880/0xx-xxx and later · up to and including FW15affected
- 750-881 and later · up to and including FW14affected
- 750-882 and later · up to and including FW14affected
- 750-885/0xx-xxx and later · up to and including FW14affected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- wago 750-8202 firmwarebefore 03.06.19_\(18\)
- wago 750-8203 firmwarebefore 03.06.19_\(18\)
- wago 750-8204 firmwarebefore 03.06.19_\(18\)
- wago 750-8206 firmwarebefore 03.06.19_\(18\)
- wago 750-8207 firmwarebefore 03.06.19_\(18\)
- wago 750-8208 firmwarebefore 03.06.19_\(18\)
- wago 750-8210 firmwarebefore 03.06.19_\(18\)
- wago 750-8211 firmwarebefore 03.06.19_\(18\)
- wago 750-8212 firmwarebefore 03.06.19_\(18\)
- wago 750-8213 firmwarebefore 03.06.19_\(18\)
- wago 750-8214 firmwarebefore 03.06.19_\(18\)
- wago 750-8216 firmwarebefore 03.06.19_\(18\)
- wago 750-8217 firmwarebefore 03.06.19_\(18\)
- wago 750-823 firmwarebefore fw08
- wago 750-829 firmwarebefore fw15
- wago 750-831 firmwarebefore fw15
- wago 750-832 firmwarebefore fw08
- wago 750-852 firmwarebefore fw15
- wago 750-862 firmwarebefore fw08
- wago 750-880 firmwarebefore fw16
Same product
wago: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-34584CODESYS V2 web server: crafted requests could trigger a buffer over-read (DoS)36Monitor
- CVE-2021-21000WAGO: PFC200 Denial of Service due to the number of connections to the runtime30Monitor
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.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);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)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log (0)
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.