CVE-2019-10712
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 · uneditedThe Web-GUI on WAGO Series 750-88x (750-330, 750-352, 750-829, 750-831, 750-852, 750-880, 750-881, 750-882, 750-884, 750-885, 750-889) and Series 750-87x (750-830, 750-849, 750-871, 750-872, 750-873) devices has undocumented service access.
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 · moderate confidenceThe WAGO 750 series PLC devices contain an undocumented service accessible through the web-based management interface. This hidden service, present across multiple device models in the 750-88x and 750-87x series, provides unauthorized access with a critical severity CVSS rating, likely enabling remote code execution or administrative access without proper authentication.
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< 06< 08< 11< 07< 07< 14< 14< 14CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the WAGO PLC model numberAccess the device's web-based management interface or check the device labeling/management console to confirm the exact model (e.g., 750-830, 750-849, 750-871, 750-872, 750-873, 750-330, 750-352, 750-829).Affected if The model number matches any of the following: 750-830, 750-849, 750-871, 750-872, 750-873, 750-330, 750-352, or 750-829.
-
Retrieve the installed firmware versionLog into the device web interface or use the WAGO management tools to view the firmware version information. This is typically found under System > Firmware or a similar diagnostics section.Affected if The firmware version is below the threshold for your specific model (750-830: <06, 750-849: <08, 750-871: <11, 750-872: <07, 750-873: <07, 750-330: <14, 750-352: <14, 750-829: <14).
-
Confirm the web-based management interface is enabledCheck the device configuration to determine if the web-based management interface (HTTP/HTTPS) is currently enabled and accessible on the device.Affected if The web-based management interface is enabled and reachable on the network.
-
Test for the undocumented service endpointUsing a web browser or HTTP client, attempt to access the device through common web paths to identify any undocumented or hidden service endpoints not documented in the official administration manual.Affected if Any undocumented service endpoints are accessible without authentication or with default credentials.
You are affected if your device is a WAGO 750 series model listed above, runs firmware below the specified version threshold, and has the web-based management interface enabled.
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.
dbcve · scoped060708
Apply vendor-provided firmware updates when available; until then, disable the web GUI interface or isolate affected devices on a restricted network segment to minimize exposure.
Firmware 06+ for 750-830, 08+ for 750-849, 11+ for 750-871, 07+ for 750-872/750-873, 14+ for 750-330/750-352/750-829
- 1. Identify the exact WAGO 750 series model number (e.g., 750-830, 750-849, etc.) from the device label or Web-GUI
- 2. Check the current firmware version via the Web-GUI (typically under System > Firmware or similar menu)
- 3. Navigate to the official WAGO download portal or contact WAGO support to obtain the firmware update for your specific model
- 4. For 750-830: upgrade to firmware version 06 or later
- 5. For 750-849: upgrade to firmware version 08 or later
- 6. For 750-871: upgrade to firmware version 11 or later
- 7. For 750-872 or 750-873: upgrade to firmware version 07 or later
- 8. For 750-330, 750-352, or 750-829: upgrade to firmware version 14 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10712 — 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-10712 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