CVE-2019-18202
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 · uneditedInformation Disclosure is possible on WAGO Series PFC100 and PFC200 devices before FW12 due to improper access control. A remote attacker can check for the existence of paths and file names via crafted HTTP requests.
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 confidenceWAGO PFC100 and PFC200 devices before FW12 contain an improper access control vulnerability in their HTTP web management interface. A remote unauthenticated attacker can send crafted HTTP requests to enumerate and discover valid file paths and names on the device, potentially revealing system configuration, credentials, or other sensitive information that could aid further attacks.
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< 03.00.35\(12\)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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify WAGO PFC device modelCheck the physical device label, review DHCP lease tables on your network DHCP server, or use network discovery tools to identify if the target device is a WAGO PFC100 or PFC200 modelAffected if Device is a WAGO PFC100 or PFC200 controller
-
Determine firmware versionAccess the device web management interface (typically HTTP on port 80) and navigate to System > Firmware or similar admin section, or check via WAGO management tools. Compare the displayed version to 03.00.35(12)Affected if Installed firmware version is below 03.00.35(12)
-
Confirm HTTP web interface is network accessibleAttempt to reach the device HTTP web interface from a network perspective (e.g., curl http://<device-ip>/) from an untrusted or external network segmentAffected if The HTTP management interface is reachable from networks outside the trusted management VLAN
-
Test for unauthenticated file path disclosureSend crafted HTTP GET requests to enumerate common file paths on the web interface (such as /, /backup/, /config/, /etc/, /web/) without providing any authentication credentialsAffected if The web server responds with directory listings, configuration files, or sensitive system information without requiring login
A user is affected if they have a WAGO PFC100 or PFC200 device running firmware version below 03.00.35(12) with the HTTP web management interface exposed to untrusted networks, allowing unauthenticated access to sensitive file paths.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data03.00.35
Upgrade WAGO PFC100/PFC200 devices to firmware version 12 or later. If immediate patching is not possible, restrict network access to the management interface using network segmentation and firewall rules to limit exposure to untrusted networks.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18202 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-18202 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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