# CVE-2021-22819: Cross-site request forgery in n/a

> Attackers can trick users into modifying settings or accounts via iframes in the web interface of Schneider EVlink charging stations.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **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:** 28 Jan 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-27h5-6x4r-4343

## What is CVE-2021-22819?

CVE-2021-22819 is a medium-severity vulnerability in n/a, published on 28 Jan 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-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 Products: EVlink City EVC1S22P4 / EVC1S7P4 (All versions prior to R8 V3.4.0.2 ), EVlink Parking EVW2 / EVF2 / EVP2PE (All versions prior to R8 V3.4.0.2), and EVlink Smart Wallbox EVB1A (All versions prior to R8 V3.4.0.2)

Weakness: CWE-1021 (Improper Restriction of Rendered UI Layers or Frames)

## Which versions are affected by CVE-2021-22819?

It affects 6 products.


Products: Schneider-Electric Evlink City Evc1s22p4 Firmware, Schneider-Electric Evlink City Evc1s7p4 Firmware, Schneider-Electric Evlink Parking Evf2 Firmware, Schneider-Electric Evlink Parking Evp2pe Firmware, Schneider-Electric Evlink Parking Evw2 Firmware, Schneider-Electric Evlink Smart Wallbox Evb1a Firmware.

## How do I fix CVE-2021-22819?

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

## Is CVE-2021-22819 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-22820](https://insights.sbomify.com/CVE-2021-22820/): Auth bypass in n/a (critical 9.8)
- [CVE-2021-22707](https://insights.sbomify.com/CVE-2021-22707/): Hardcoded credentials in EVlink City (EVC1S22P4 / EVC1S7P4 all versions prior to R8 V3.4.0.1), EVlink Parking (EVW2 / EVF2 / EV.2 all versions prior to R8 V3.4.0.1), and EVlink Smart Wallbox (EVB1A all versions prior to R8 V3.4.0.1 ) (critical 9.8)
- [CVE-2021-22727](https://insights.sbomify.com/CVE-2021-22727/): Weak cryptography in EVlink City (EVC1S22P4 / EVC1S7P4 all versions prior to R8 V3.4.0.1), EVlink Parking (EVW2 / EVF2 / EV.2 all versions prior to R8 V3.4.0.1), and EVlink Smart Wallbox (EVB1A all versions prior to R8 V3.4.0.1 ) (critical 9.8)
- [CVE-2021-22729](https://insights.sbomify.com/CVE-2021-22729/): Hardcoded credentials in EVlink City (EVC1S22P4 / EVC1S7P4 all versions prior to R8 V3.4.0.1), EVlink Parking (EVW2 / EVF2 / EV.2 all versions prior to R8 V3.4.0.1), and EVlink Smart Wallbox (EVB1A all versions prior to R8 V3.4.0.1 ) (critical 9.8)
- [CVE-2021-22730](https://insights.sbomify.com/CVE-2021-22730/): Hardcoded credentials in EVlink City (EVC1S22P4 / EVC1S7P4 all versions prior to R8 V3.4.0.1), EVlink Parking (EVW2 / EVF2 / EV.2 all versions prior to R8 V3.4.0.1), and EVlink Smart Wallbox (EVB1A all versions prior to R8 V3.4.0.1 ) (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-22819 and fix it if it is affected.

What it is: CVE-2021-22819 is a medium-severity vulnerability in n/a, published on 28 Jan 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-2021-22819 in the wild and no public exploit code.

Affected product: n/a. 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-2021-22819/ (Markdown: https://insights.sbomify.com/CVE-2021-22819/index.md)
```

## Sources

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

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