CVE-2023-1698
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 · uneditedIn multiple products of WAGO a vulnerability allows an unauthenticated, remote attacker to create new users and change the device configuration which can result in unintended behaviour, Denial of Service and full system compromise.
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 confidenceIn multiple WAGO industrial control products, an authentication bypass vulnerability allows an unauthenticated remote attacker to create new administrative users and modify device configuration, leading to potential full system compromise.
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>= 20, <= 23= 22>= 20, <= 23>= 20, <= 23= 22= 22= 22CVSS 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.1/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 device modelAccess the device web interface or check the device label/sticker to determine the exact model (Compact Controller 100, Edge Controller, PFC100, PFC200, Touch Panel 600 Advanced/Marine/Standard)Affected if The device is any of the affected WAGO models listed in the CVE
-
Check the firmware versionLog into the device web interface and navigate to the firmware or system information page, or use the WAGO tool 'wagoadm' via CLI with command 'wagoadm -v' to retrieve the firmware versionAffected if The firmware version matches the affected ranges: 20-23 for Compact Controller 100/PFC100/PFC200, or exactly version 22 for Edge Controller/Touch Panel 600 variants
-
Verify if the web-based management interface is accessible remotelyAttempt to access the device IP from an external network or check firewall rules to determine if HTTP/HTTPS ports (typically 80/443) are exposed to untrusted networksAffected if The web management interface is reachable from untrusted networks without VPN or proper network segmentation
-
Audit existing user accounts for unauthorized administrative usersLog into the device as an administrator and navigate to the user management or authentication settings page to review all accounts with administrative privilegesAffected if Unexpected or unknown user accounts with administrative access exist on the device
A user is affected if they have a WAGO device from the affected product line running firmware version 20-23 (or 22 specifically for Edge Controller and Touch Panel variants) with the management interface externally accessible.
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 dataIsolate affected WAGO devices behind a firewall with strict access controls, disable remote management interfaces if possible, and apply vendor-supplied firmware patches when available.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1698 — 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-2023-1698 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