CVE-2022-22807
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 CWE-1021 Improper Restriction of Rendered UI Layers or Frames vulnerability exists that could cause unintended modifications of the product settings or user accounts when deceiving the user to use the web interface rendered within iframes. Affected Product: EcoStruxure EV Charging Expert (formerly known as EVlink Load Management System): (HMIBSCEA53D1EDB, HMIBSCEA53D1EDS, HMIBSCEA53D1EDM, HMIBSCEA53D1EDL, HMIBSCEA53D1ESS, HMIBSCEA53D1ESM, HMIBSCEA53D1EML) (All Versions prior to SP8 (Version 01) V4.0.0.13)
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 confidenceThis is a Clickjacking (CWE-1021) vulnerability in the EcoStruxure EV Charging Expert web interface. Attackers can embed the application's web interface within hidden or disguised iframes to trick authenticated users into unknowingly modifying product settings or user account configurations through UI redressing attacks.
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< 4.0.0.13< 4.0.0.13< 4.0.0.13< 4.0.0.13< 4.0.0.13< 4.0.0.13< 4.0.0.13CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/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 device modelAccess the device web interface or system information page and locate the exact model identifier. It should be one of: Hmibscea53d1edb, Hmibscea53d1eds, Hmibscea53d1edm, Hmibscea53d1edl, Hmibscea53d1ess, Hmibscea53d1esm, or Hmibscea53d1eml.Affected if The device model is any of the listed Hmibscea53d1ed* variants.
-
Check the installed firmware versionNavigate to the firmware or system version section within the web interface, or query the device API if available. Compare the version number to 4.0.0.13.Affected if The firmware version is lower than 4.0.0.13.
-
Inspect HTTP response headers for X-Frame-OptionsUse a browser developer tool or command-line tool (e.g., curl -I) to fetch the login or main page of the web interface. Look for the X-Frame-Options header in the response.Affected if The X-Frame-Options header is absent, or set to a permissive value such as ALLOW-FROM for untrusted domains.
-
Inspect HTTP response headers for Content-Security-Policy frame-ansectorsReview the HTTP headers of responses from the web interface. Look for a Content-Security-Policy header that includes the frame-ancestors directive.Affected if The Content-Security-Policy header is absent, or does not include the frame-ancestors directive to restrict framing.
A user is affected if they have a device model from the Hmibscea53d1ed* family running firmware version below 4.0.0.13, AND the web interface responses lack X-Frame-Options and CSP frame-ancestors headers.
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 · scoped4.0.0.13
Implement X-Frame-Options: DENY or SAMEORIGIN header, and/or Content-Security-Policy with frame-ancestors directive to prevent the application from being rendered in iframes on untrusted domains.
SP8 (Version 01) V4.0.0.13 or later
- 1. Identify the specific model number (HMIBSCEA53D1EDx) of the affected EcoStruxure EV Charging Expert device
- 2. Download the firmware version 4.0.0.13 (SP8 Version 01) or later from download.schneider-electric.com
- 3. Review the Schneider Electric firmware upgrade instructions for the specific model
- 4. Backup current device configuration before performing the upgrade
- 5. Apply the firmware upgrade following the manufacturer's documented procedure
- 6. Verify the device is running firmware version 4.0.0.13 or later after upgrade
- 7. Confirm the web interface properly implements X-Frame-Options or Content Security Policy (CSP) frame-ancestors to mitigate clickjacking
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22807 — 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-22807 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