CVE-2022-22511
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 · uneditedVarious configuration pages of the device are vulnerable to reflected XSS (Cross-Site Scripting) attacks. An authorized attacker with user privileges may use this to gain access to confidential information on a PC that connects to the WBM after it has been compromised.
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 confidenceReflected XSS vulnerability in multiple configuration pages of the device's Web-based Management (WBM) interface. An authorized attacker with user-level privileges can inject malicious scripts through vulnerable parameters, which execute in the browser of users accessing compromised WBM pages, allowing exfiltration of confidential data from connected PCs.
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>= fw16, < fw22>= fw16, < fw22>= fw16, < fw22>= fw16, < fw22>= fw16, < fw22>= fw16, < fw22>= fw16, < fw22>= fw16, < fw22CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 Wago device modelLocate the product label on the device or access the device's system information page in WBM to determine the exact model number (e.g., 750-8100, 762-4205/8000 002)Affected if The device model matches one of: 750-8100, 750-8101, 750-8102, 751-9301, 750-8202, 762-4205/8000 002, 762-4206/8000 002, or 762-4305/8000 002
-
Check the installed firmware versionAccess the device's WBM interface and navigate to the firmware or system information page to read the current firmware version. Alternatively, use the device's command-line interface or management tool if WBM is not accessible.Affected if The firmware version is greater than or equal to fw16 but less than fw22 (e.g., fw17, fw18, fw19, fw20, fw21)
-
Verify WBM interface is enabled and accessibleAttempt to access the device's web-based management interface via HTTP/HTTPS using the device's IP address. Check if the login page loads and user-level authentication is possible.Affected if The WBM interface is accessible and accepts user-level credentials, indicating the vulnerable configuration pages are exposed
-
Confirm user-level access capabilityLog into WBM with a standard user account (not administrator) to verify that configuration pages are accessible at user privilege levelAffected if Configuration pages in WBM are accessible with user-level privileges, which is required for the reflected XSS to be exploitable
The device is affected if it is one of the listed Wago models, runs firmware version fw16 through fw21 (inclusive), and has the WBM interface accessible with user-level privileges.
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.
dbcve · scopedImplement proper input validation and output encoding on all user-supplied parameters in configuration pages; deploy Content Security Policy headers to mitigate XSS execution.
Firmware fw22 or later
- Identify the affected Siemens/Ridgeyon device model from the list (750 8100, 750 8101, 750 8102, 751 9301, 750 8202, 762 4205/8000 002, 762 4206/8000 002, or 762 4305/8000 002)
- Access the device's web-based management (WBM) interface
- Navigate to the firmware version or system information page to confirm the current firmware version is between fw16 and fw21 (inclusive)
- Obtain the fixed firmware version fw22 or later from the official vendor (Siemens or Ridgeyon support channels)
- Review the vendor's firmware upgrade instructions for your specific device model
- Back up the current device configuration if supported by the firmware
- Upload and apply the fw22 or later firmware following the vendor's documented procedure
- After upgrade, verify the firmware version has been successfully updated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22511 — 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-22511 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