CVE-2022-50926
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 750-8212 PFC200 G2 2ETH RS firmware contains a privilege escalation vulnerability that allows attackers to manipulate user session cookies. Attackers can modify the cookie's 'name' and 'roles' parameters to elevate from ordinary user to administrative privileges without authentication.
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 confidenceWAGO 750-8212 PFC200 G2 2ETH RS firmware contains a privilege escalation vulnerability where attackers can manipulate user session cookies by modifying the 'name' and 'roles' parameters. This allows unauthenticated attackers to elevate from ordinary user privileges to administrative access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the device label, web interface, or SNMP inventory for the exact model number 750-8212 PFC200 G2 2ETH RSAffected if The device is a WAGO 750-8212 PFC200 G2 2ETH RS controller
-
Determine the firmware versionAccess the device web interface and navigate to the System > Firmware or About section, or use the command line (e.g., 'plcinfo' or checking /etc/version) to retrieve the installed firmware versionAffected if The firmware version is unpatched and falls within the vulnerable range (compare your version against any vendor-released patches for CVE-2022-50926)
-
Verify the web management interface is enabledCheck if HTTP/HTTPS web management is accessible on the device (typically ports 80/443 or 8080/8443). Confirm the interface is reachable from your network segmentAffected if The web management interface is exposed and accessible
-
Confirm cookie-based session authentication is in useLog into the device web interface with a standard user account, then inspect browser developer tools (Application > Cookies) or capture network traffic to observe session cookies. Look for cookies containing 'name' and 'roles' parametersAffected if Session cookies contain manipulatable 'name' and 'roles' parameters that can be modified to escalate privileges
You are affected if you have a WAGO 750-8212 PFC200 G2 device with an unpatched firmware version and its web interface is accessible with cookie-based authentication that allows modification of the 'name' and 'roles' parameters.
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 dataApply vendor firmware patches when available and implement network segmentation to limit exposure to trusted users only, as the vulnerability allows complete privilege escalation without authentication.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-50926 — 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-2022-50926 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