dbcve.org
0852 1328 FirmwareOperating system · Wago

CVE-2025-41730

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-10
Fix available
A fix is available. Upgrade to 02.64 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
An unauthenticated remote attacker can abuse unsafe sscanf calls within the check_account() function to write arbitrary data into fixed-size stack buffers which leads to full device 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 confidence

An unauthenticated remote attacker can exploit unsafe sscanf calls within the check_account() function to perform stack-based buffer overflows, allowing arbitrary data to be written beyond buffer boundaries. This memory corruption leads to full device compromise, likely through code execution on the stack.

MitigationReplace unsafe sscanf calls in check_account() with bounds-checked alternatives (e.g., snprintf with width specifiers, or explicit length validation before sscanf) and implement proper input validation. Given the critical CVSS and device compromise scope, a firmware update with thorough regression testing is required.

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 1328 FirmwareOperating system
Affected:< 02.64
0852 1322 FirmwareOperating system
Affected:< 02.64

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 device model
    Locate the Wago device model number on the hardware label or via the device's web interface or management console. Confirm it is either model 0852 1328 or 0852 1322.
    Affected if The device is a Wago 0852 1328 or 0852 1322 unit.
  2. Check the installed firmware version
    Access the device's web interface, management console, or use the vendor-provided tool (such as WAGO I/O Check or PFC Firmware Update Tool) to retrieve the current firmware version. Compare it against the affected version threshold of 02.64.
    Affected if The firmware version is below 02.64 (for example, 02.63, 02.60, etc.).
  3. Identify the check_account service availability
    Determine if the device exposes any network service (such as HTTP, HTTPS, or a proprietary protocol) that utilizes the check_account() function. Review network configuration and firewall rules to see if remote unauthenticated access to this service is possible.
    Affected if The check_account() function is accessible over the network without authentication and the firmware version is below 02.64.
  4. Review network exposure of management interfaces
    Scan the device's open ports and services using a network scanner. Check if port 80, 443, or other management ports are exposed to untrusted networks. Verify if the device is behind a properly configured firewall.
    Affected if Management interfaces containing the vulnerable check_account() function are exposed to untrusted networks and the firmware version is below 02.64.

You are affected if your Wago 0852 1328 or 0852 1322 device runs firmware version below 02.64 and the check_account() function is network-accessible without authentication.

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 02.64 or later
Fixed in 02.64
Interim mitigation

Replace unsafe sscanf calls in check_account() with bounds-checked alternatives (e.g., snprintf with width specifiers, or explicit length validation before sscanf) and implement proper input validation. Given the critical CVSS and device compromise scope, a firmware update with thorough regression testing is required.

Recommended fix High confidence

Firmware 02.64 for models 0852 1328 and 0852 1322

  1. Identify the specific device model (0852 1328 or 0852 1322) requiring remediation
  2. Access the device administration interface or CLI to determine the current firmware version
  3. Obtain firmware version 02.64 or later from the official vendor support portal or trusted distribution channel
  4. Backup the current device configuration if supported by the platform
  5. Upload and apply firmware version 02.64 following the vendor's documented upgrade procedure (typically via web UI, TFTP, or USB)
  6. Allow the device to fully reboot and complete the firmware installation process
  7. Verify the device is running firmware version 02.64 or later
  8. Confirm the check_account() function is no longer accessible to unauthenticated users

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

Fix this in 0852 1328 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41730 — 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-2025-41730 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