CVE-2023-3379
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 · uneditedWago web-based management of multiple products has a vulnerability which allows an local authenticated attacker to change the passwords of other non-admin users and thus to escalate non-root privileges.
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 confidenceThis is a privilege escalation vulnerability in Wago web-based management interfaces across multiple products. A locally authenticated attacker with non-admin privileges can change passwords of other non-admin users, enabling escalation from their current non-root access level to higher privileges within the application.
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<= 25<= 25< 22= 22< 22= 22= 23= 24<= 25<= 25<= 25CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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's web-based management interface or check the physical device label to confirm the exact model (e.g., Compact Controller 100, Edge Controller, PFC100, PFC200, Touch Panel 600 variants).Affected if The device is one of the affected models listed in the CVE.
-
Determine the installed firmware versionLog into the Wago web-based management interface and navigate to the System or Firmware Information section to view the current firmware version. Alternatively, check via the device's CLI or diagnostic page.Affected if The firmware version falls within these affected ranges: Compact Controller 100 <= 25, Edge Controller <= 25, PFC100 < 22 or = 22, PFC200 < 22, = 22, = 23, or = 24, Touch Panel 600 (all variants) <= 25.
-
Confirm the web-based management interface is enabledVerify that the web-based management interface (HTTP/HTTPS) is active and accessible on the device. Check the device's network settings or service status.Affected if The web-based management interface is enabled - this is required for the vulnerability to be exploitable.
-
Review existing user accountsAccess the user management or account settings page in the web interface to list all configured non-admin user accounts.Affected if Multiple non-admin user accounts exist - the vulnerability allows one non-admin user to change another non-admin user's password, enabling privilege escalation.
A user is affected if they have a Wago device from the affected product list with a firmware version within the specified ranges AND the web-based management interface is enabled with more than one non-admin user account configured.
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 data22
Restrict access to the web-based management interface to trusted users only and apply vendor-provided patches when available. Monitor for unauthorized password modification attempts.
- Consultation6.0 h
- Implementation8.0 h
- Testing4.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 $6,048.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3379 — 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-3379 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