# CVE-2022-22808: Cross-site request forgery in 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)

> Remote attackers can bypass CSRF protections to gain unauthorized access to the EcoStruxure EV Charging Expert system.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-p6hc-w7h4-q55x

## What is CVE-2022-22808?

CVE-2022-22808 is a high-severity vulnerability in 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), published on 9 Feb 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A CWE-352: Cross-Site Request Forgery (CSRF) exists that could cause a remote attacker to gain unauthorized access to the product when conducting cross-domain attacks based on same-origin policy or cross-site request forgery protections bypass. 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)

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2022-22808?

It affects 7 products.


Products: Schneider-Electric Hmibscea53d1edb Firmware, Schneider-Electric Hmibscea53d1edl Firmware, Schneider-Electric Hmibscea53d1edm Firmware, Schneider-Electric Hmibscea53d1eds Firmware, Schneider-Electric Hmibscea53d1eml Firmware, Schneider-Electric Hmibscea53d1esm Firmware, Schneider-Electric Hmibscea53d1ess Firmware.

## How do I fix CVE-2022-22808?

No fix has been published for CVE-2022-22808 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-22808 being exploited?

There is no known exploitation of CVE-2022-22808 in the wild and no public exploit code.

## Other vulnerabilities in 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)

- [CVE-2022-22807](https://insights.sbomify.com/CVE-2022-22807/): Cross-site request forgery in 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) (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-22808 and fix it if it is affected.

What it is: CVE-2022-22808 is a high-severity vulnerability in 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), published on 9 Feb 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-22808 in the wild and no public exploit code.

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). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-22808/ (Markdown: https://insights.sbomify.com/CVE-2022-22808/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-22808
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-22808
- OSV: https://osv.dev/vulnerability/CVE-2022-22808

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-22808/
Summaries are generated and may contain mistakes; the official description above is the record.