dbcve.org
0852 0602 FirmwareOperating system · Wago

CVE-2023-4149

CRITICAL · 9.8 CVSS v3.1 Published 2023-11-21
Fix available
A fix is available. Upgrade to 1.0.6.s0 / 1.2.5.s0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability in the web-based management allows an unauthenticated remote attacker to inject arbitrary system commands and gain full system control. Those commands are executed with root privileges. The vulnerability is located in the user request handling of the web-based management.

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 confidence

This is a command injection vulnerability in the web-based management interface where user requests are processed. An unauthenticated remote attacker can inject arbitrary system commands through the web interface, which are then executed with root privileges, providing full system control.

MitigationApply vendor patches immediately. If no patch is available, disable or restrict access to the web-based management interface using network segmentation or firewall rules to prevent untrusted network access.

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
0852 0602 FirmwareOperating system
Affected:< 1.0.6.s0
0852 0603 FirmwareOperating system
Affected:< 1.0.6.s0
0852 1605 FirmwareOperating system
Affected:< 1.2.5.s0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Wago device model
    Locate the device label or access the device inventory/management console to confirm the exact model number (0852 0602, 0852 0603, or 0852 1605)
    Affected if The model is one of the three affected variants (0852 0602, 0852 0603, or 0852 1605)
  2. Check the installed firmware version
    Access the device web interface, CLI, or management console to retrieve the current firmware version information
    Affected if For model 0852 0602 or 0852 0603: firmware version is lower than 1.0.6.s0; for model 0852 1605: firmware version is lower than 1.2.5.s0
  3. Determine if the web-based management interface is enabled
    Check the device configuration or network settings to verify whether the web-based management interface is currently active
    Affected if The web-based management interface is enabled and accessible
  4. Assess network exposure of the management interface
    Review firewall rules, network configuration, or access control lists to determine if the web management interface is reachable from untrusted networks
    Affected if The web interface is exposed to untrusted or public networks without proper access restrictions

A user is affected if they have a Wago 0852 0602, 0852 0603, or 0852 1605 device running firmware below the respective threshold (1.0.6.s0 or 1.2.5.s0) with the web-based management interface enabled and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.0.6.s0 / 1.2.5.s0 or later
Fixed in 1.0.6.s01.2.5.s0
Interim mitigation

Apply vendor patches immediately. If no patch is available, disable or restrict access to the web-based management interface using network segmentation or firewall rules to prevent untrusted network access.

Recommended fix High confidence

Firmware 1.0.6.s0 (for 0852 0602 and 0852 0603); Firmware 1.2.5.s0 (for 0852 1605)

  1. 1. Identify the specific device model number (0852 0602, 0852 0603, or 0852 1605)
  2. 2. Check the current firmware version on the device through the web-based management interface or CLI
  3. 3. Navigate to the vendor's support page or download center (cert.vde.com)
  4. 4. Download the appropriate fixed firmware: version 1.0.6.s0 for models 0852 0602 and 0852 0603, or version 1.2.5.s0 for model 0852 1605
  5. 5. Review the vendor's firmware upgrade instructions and release notes
  6. 6. Backup the current device configuration if supported
  7. 7. Upload and apply the new firmware following the vendor's documented procedure
  8. 8. Verify the firmware version was successfully updated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in 0852 0602 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4149 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-4149 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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