CVE-2022-45139
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 · uneditedA CORS Misconfiguration in the web-based management allows a malicious third party webserver to misuse all basic information pages on the webserver. In combination with CVE-2022-45138 this could lead to disclosure of device information like CPU diagnostics. As there is just a limited amount of information readable the impact only affects a small subset of confidentiality.
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 confidenceA CORS misconfiguration in the web-based management interface allows malicious third-party websites to access basic information pages due to overly permissive Access-Control-Allow-Origin headers. When chained with CVE-2022-45138, this enables disclosure of device information such as CPU diagnostics.
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>= 16, < 22= 22= 23>= 18, < 22= 22= 23>= 16, < 22= 22= 23>= 16, < 22= 22= 23>= 16, < 22= 22= 23>= 16, < 22= 22= 23>= 16, < 22= 22= 23CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 device model and firmware versionAccess the web-based management interface or check system information pages (typically at / or /info) to retrieve the exact firmware version and model numberAffected if Firmware version matches >= 16 and < 22, or equals 22, or equals 23 for the listed Wago models (751 9301, 752 8303/8000 002, PFC100, PFC200, Touch Panel 600 Advanced/Marine/Standard)
-
Verify web management interface is accessibleAttempt to access the web-based management interface via HTTP/HTTPS on the deviceAffected if The web management interface is enabled and reachable on the network
-
Test CORS header configurationSend a cross-origin HTTP request with an arbitrary Origin header (e.g., Origin: http://malicious-site.com) to the management interface endpoints and inspect the Access-Control-Allow-Origin response headerAffected if The Access-Control-Allow-Origin header reflects the arbitrary Origin value (e.g., contains the malicious origin or is set to a wildcard *) instead of being restricted to specific trusted origins
The environment is affected if the Wago device runs a firmware version in the ranges >= 16/< 22, = 22, or = 23 AND the web management interface is accessible with permissive CORS headers that allow arbitrary origins.
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 data22
Restrict CORS headers to whitelist specific trusted origins and reject requests from untrusted domains. Validate the Access-Control-Allow-Origin header against an explicit allowlist rather than reflecting arbitrary origins.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45139 — 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-45139 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