dbcve.org
751 9301 FirmwareOperating system · Wago

CVE-2022-45138

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 of the web-based management can be used by unauthenticated users, although only authenticated users should be able to use the API. The vulnerability allows an unauthenticated attacker to read and set several device parameters that can lead to full compromise of the device.

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 web-based management interface's configuration backend fails to enforce authentication, allowing unauthenticated users to access the API and read/set device parameters. This authentication bypass enables attackers to modify device configuration leading to full device compromise.

MitigationImplement proper authentication enforcement on all backend API endpoints and ensure unauthenticated requests are rejected at the entry point of the management interface.

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. Check the device firmware version
    Access the device's web management interface or use the device's administrative console to retrieve the firmware version. This is typically found in System > Information or Settings > Device Info.
    Affected if The installed firmware version falls within these ranges: >= 16 and < 22, OR equals 22, OR equals 23 (for your specific device model)
  2. Verify if the web management interface is accessible
    Open a web browser and navigate to the device's IP address using HTTP or HTTPS. Confirm the login page or management interface loads.
    Affected if The management interface is reachable on the network and responds to requests
  3. Test API endpoint authentication enforcement
    Using a tool like curl or a web proxy, send an HTTP request to a typical API endpoint such as /api/system/info or /api/config without providing any authentication credentials or session cookies.
    Affected if The API returns actual device configuration data, system information, or accepts configuration changes without requiring login credentials
  4. Confirm the specific device model is affected
    Identify the exact Wago device model (751 9301, 752 8303/8000 002, PFC100, PFC200, Touch Panel 600 Advanced/Marine/Standard) through the web interface or device labeling.
    Affected if The device model matches one of the affected products listed in the CVE

A user is affected if they are running one of the listed Wago device models with firmware versions >= 16 and < 22, equal to 22, or equal to 23, AND the API endpoints are 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 22 or later
Fixed in 22
Interim mitigation

Implement proper authentication enforcement on all backend API endpoints and ensure unauthenticated requests are rejected at the entry point of the management interface.

Recommended fix Moderate confidence

Firmware version 24 or later (verify latest stable release from WAGO vendor)

  1. 1. Identify the specific device model from the affected product list (751 9301, 752 8303/8000 002, Pfc100, Pfc200, Touch Panel 600 Advanced/Marine/Standard)
  2. 2. Check the current firmware version of the device through the web interface or device documentation
  3. 3. Download the latest firmware version >= 24 from the official WAGO or vendor support portal
  4. 4. Back up the current device configuration before upgrading
  5. 5. Upload and install the new firmware via the device's web-based management interface or appropriate firmware update tool
  6. 6. Verify the upgrade was successful and the device is functioning normally
  7. 7. After upgrade, confirm the vulnerability is fixed by verifying that the configuration API now requires authentication
Caveat Review vendor release notes for any configuration changes or breaking changes between current and new firmware versions before upgrading

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

Fix this in 751 9301 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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