dbcve.org
751 9301 FirmwareOperating system · Wago

CVE-2022-45140

CRITICAL · 9.8 CVSS v3.1 Published 2023-02-27
Fix available
A fix is available. Upgrade to 22 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
The configuration backend allows an unauthenticated user to write arbitrary data with root privileges to the storage, which could lead to unauthenticated remote code execution 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 confidence

The configuration backend lacks authentication controls, allowing any unauthenticated user to write arbitrary data with root privileges directly to storage. This enables attackers to inject malicious configuration, scripts, or code that gets executed with root-level permissions, achieving unauthenticated remote code execution and full system compromise.

MitigationImmediately restrict the configuration backend to require authenticated access, implement proper authorization checks on write operations, and validate/sanitize all data before storage. Network-level filtering may be needed as an interim control.

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
751 9301 FirmwareOperating system
Affected:>= 16, < 22= 22= 23
752 8303\/8000 002 FirmwareOperating system
Affected:>= 18, < 22= 22= 23
Pfc100 FirmwareOperating system
Affected:>= 16, < 22= 22= 23
Pfc200 FirmwareOperating system
Affected:>= 16, < 22= 22= 23
Touch Panel 600 Advanced FirmwareOperating system
Affected:>= 16, < 22= 22= 23
Touch Panel 600 Marine FirmwareOperating system
Affected:>= 16, < 22= 22= 23
Touch Panel 600 Standard FirmwareOperating system
Affected:>= 16, < 22= 22= 23

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 Wago device model
    Determine the exact model number of the Wago device (e.g., 751 9301, 752 8303/8000 002, PFC100, PFC200, Touch Panel 600 Advanced/Marine/Standard)
    Affected if The device model matches one of the affected product families listed in the CVE
  2. Check firmware version
    Retrieve the installed firmware version from the device system information or management interface
    Affected if The firmware version is >= 16 and < 22, or equals 22, or equals 23
  3. Locate configuration backend service
    Identify which service or port handles the configuration backend on the device (commonly the web-based management or configuration service)
    Affected if The configuration backend service is running and exposed on the device
  4. Test unauthenticated configuration write access
    Attempt to send a write request to the configuration backend without providing any authentication credentials
    Affected if The backend accepts and processes unauthenticated write operations
  5. Verify root-level privilege on configuration writes
    Check whether write operations to the configuration backend execute with root or elevated privileges
    Affected if Unauthenticated configuration writes execute with root-level permissions

A defender is affected if they have a Wago device from the listed product families running firmware version 16 or higher, and the configuration backend allows unauthenticated write operations with root privileges.

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

Immediately restrict the configuration backend to require authenticated access, implement proper authorization checks on write operations, and validate/sanitize all data before storage. Network-level filtering may be needed as an interim control.

Recommended fix Moderate confidence

Firmware version 24 or later (first fixed release)

  1. 1. Identify the exact device model (751 9301, 752 8303/8000 002, PFC100, PFC200, or Touch Panel 600 variant) from the affected product list
  2. 2. Access the device's web interface or management console
  3. 3. Navigate to the firmware update section
  4. 4. Download the latest firmware version from the vendor's official support site (cert.vde.com or manufacturer website)
  5. 5. Upload and apply the firmware update, ensuring stable power during the process
  6. 6. Verify the firmware version after update to confirm the patch was applied
  7. 7. After upgrading, verify that the configuration backend now requires authentication
Caveat Review release notes for any configuration or feature changes between current and new firmware version

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

Fix this in 751 9301 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,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 $15,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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