dbcve.org
Evlink City Evc1s22p4 FirmwareOperating system · Schneider Electric

CVE-2021-22723

MEDIUM · 6.1 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 →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 (Cross-siteScripting) through Cross-Site Request Forgery (CSRF) 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 allow an attacker to impersonate the user who manages the charging station or carry out actions on their behalf when crafted malicious parameters are submitted to the charging station web server.

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 (CWE-79) exploitable via Cross-Site Request Forgery (CSRF) exists in the web server of EVlink charging stations. Attackers can submit malicious parameters that persist on the web interface and execute in the context of an authenticated administrator's session, allowing impersonation or unauthorized actions.

MitigationUpdate affected charging station firmware to R8 V3.4.0.1 or later to obtain the vendor patch. If immediate update is not possible, consider network segmentation and monitoring for anomalous requests to the web server.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 the EVlink charging station model
    Locate the device label or access the device web interface to confirm the exact model number (Evc1s22p4, Evc1s7p4, Evw2, Evf2, Ev.2, or Evb1a).
    Affected if The device model is one of the six affected models listed in the CVE.
  2. Check the installed firmware version
    Access the device web interface (typically via HTTP/HTTPS on the local network) and navigate to the firmware or system information page, or use the device's administrative console to retrieve the firmware version string.
    Affected if The firmware version is below r8_v3.4.0.1 (for example, r8_v3.3.x or earlier).
  3. Verify the web server is accessible
    Attempt to reach the device web interface by entering its IP address in a web browser. Confirm that the login or administrator portal is reachable over HTTP/HTTPS.
    Affected if The web interface is exposed and an administrator can authenticate to the device.
  4. Inspect stored web parameters for injection points
    Log into the web interface as an administrator and review any user-editable fields (such as station name, network settings, or configuration parameters). Submit benign test input and verify if the values are reflected in the page without proper sanitization.
    Affected if User-supplied values are stored and displayed back in the interface without encoding or sanitization, indicating potential XSS vulnerability.

You are affected if your EVlink charging station model matches one of the six listed products and the installed firmware version is earlier than r8_v3.4.0.1 with the web interface enabled.

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

Update affected charging station firmware to R8 V3.4.0.1 or later to obtain the vendor patch. If immediate update is not possible, consider network segmentation and monitoring for anomalous requests to the web server.

Fix this in Evlink City Evc1s22p4 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22723 — 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-22723 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