Skip to content
IoT

CVE-2022-50926

8.7
High
EPSS 0.55%Jan 14, 2026

Privilege escalation in WAGO PFC200 G2 via session cookie tampering.

common questions

Is CVE-2022-50926 being exploited?

Not confirmed. CVE-2022-50926 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.55% probability of exploitation in the next 30 days.

How severe is CVE-2022-50926?

CVE-2022-50926 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2022-50926?

Not known from our data. No patch reference has been recorded for CVE-2022-50926, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2022-50926 affect?

CVE-2022-50926 affects WAGO 750-8212 PFC200 G2 2ETH RS firmware. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2022-50926?

Apply firmware patch when available; limit admin access.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
WAGO 750-8212 PFC200 G2 2ETH RS firmware
impact

Attackers can elevate from user to admin by modifying 'name' and 'roles' cookies without authentication.

action required

Immediate action required

affected versions
Wago WAGO 750-8212 PFC200
  • affectedFirmware version 03.05.10(17)

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free