dbcve.org
Evlink City Evc1s22p4 FirmwareOperating system · Schneider Electric

CVE-2021-22722

MEDIUM · 5.4 CVSS v3.1 Published 2021-07-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
A CWE-79: Improper Neutralization of Input During Web Page Generation ('Stored Cross-site Scripting') vulnerability exists 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 ) that could cause code injection when importing a CSV file or changing station parameters.

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 confidence

A stored Cross-Site Scripting (XSS) vulnerability exists in Schneider Electric EVlink charging station web interfaces. The vulnerability allows injection of malicious scripts through CSV file imports or when modifying station parameters. Since the malicious payload is stored and later rendered in the web page without proper sanitization, any user viewing the affected interface could have the script execute in their browser context.

MitigationUpgrade EVlink firmware to version R8 V3.4.0.1 or later to receive the patch. Until then, restrict administrative web interface access to trusted users only and validate all CSV imports in a sandboxed environment before production use.

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
Evlink City Evc1s22p4 FirmwareOperating system
Affected:< r8_v3.4.0.1
Evlink City Evc1s7p4 FirmwareOperating system
Affected:< r8_v3.4.0.1
Evlink Parking Evw2 FirmwareOperating system
Affected:< r8_v3.4.0.1
Evlink Parking Evf2 FirmwareOperating system
Affected:< r8_v3.4.0.1
Evlink Parking Ev.2 FirmwareOperating system
Affected:< r8_v3.4.0.1
Evlink Smart Wallbox Evb1a FirmwareOperating system
Affected:< r8_v3.4.0.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify EVlink device model and firmware version
    Access the device web interface and navigate to the About or System Information page, or check the device configuration menu for the firmware version string (such as r8_vX.X.X.X)
    Affected if The firmware version displayed is below r8_v3.4.0.1 and the model matches Evc1s22p4, Evc1s7p4, Evw2, Evf2, Ev.2, or Evb1a
  2. Confirm web interface is accessible
    Attempt to reach the device web interface via its configured IP address or hostname using a web browser
    Affected if The web interface loads and is reachable on the network (the XSS only affects users who can access and view the web interface)
  3. Verify CSV import feature availability
    In the web interface, navigate to the configuration, settings, or import/export sections to see if CSV file import functionality exists
    Affected if CSV import feature is present and accessible (this is one of the documented attack vectors for this XSS)
  4. Check network exposure of administrative interface
    Review network configuration, firewall rules, or access control lists to determine if the web interface is exposed to untrusted network segments or the internet
    Affected if The administrative web interface is accessible from untrusted networks or shared network segments where untrusted users could view the interface and trigger the stored XSS

A user is affected if their EVlink device runs firmware version r8_v3.4.0.1 or lower from the listed product models and the web interface with CSV import capability is accessible to users who could inject malicious scripts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade EVlink firmware to version R8 V3.4.0.1 or later to receive the patch. Until then, restrict administrative web interface access to trusted users only and validate all CSV imports in a sandboxed environment before production use.

Fix this in Evlink City Evc1s22p4 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22722 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-22722 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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