dbcve.org
Evlink City Evc1s22p4 FirmwareOperating system · Schneider Electric

CVE-2021-22726

HIGH · 8.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 →
87/100
Remediation priority · High
Remotely reachable Zero-click

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-918: Server-Side Request Forgery (SSRF) 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 perform unintended actions or access to data 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 Server-Side Request Forgery (SSRF) vulnerability exists in the web server of Schneider Electric EVlink charging stations (City, Parking, and Smart Wallbox). Attackers can submit crafted malicious parameters to the charging station web server to trigger the server to make unintended requests, potentially allowing unauthorized data access or actions on internal systems.

MitigationApply the vendor patch (R8 V3.4.0.1 or later) to all affected EVlink charging station models. If patching is not immediately feasible, implement network segmentation and restrict the charging station web server's outbound network access to prevent SSRF exploitation against internal systems.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checks

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

  1. Identify the EVlink model
    Locate the charging station model label (Evlink City Evc1s22p4, Evc1s7p4; Evlink Parking Evw2, Evf2, Ev.2; or Evlink Smart Wallbox Evb1a) either on the physical unit or via the web interface login page.
    Affected if The model is one of the six affected models listed in the CVE.
  2. Check firmware version via web interface
    Log into the charging station web interface and navigate to the System Information or About page to view the installed firmware version.
    Affected if The firmware version is any version prior to r8_v3.4.0.1 (for example, r8_v3.3.x, r8_v3.2.x, or earlier).
  3. Verify web server is enabled
    Attempt to access the charging station web server via HTTP/HTTPS on the expected management port (typically port 80 or 443). If a login page or web response is returned, the web server is enabled.
    Affected if The web server responds and is accessible on the network.
  4. Check web server network exposure
    Review network firewall rules or access control lists to determine if the web server management interface is exposed to untrusted networks (such as the internet or guest networks).
    Affected if The web interface is reachable from networks other than a trusted administrative network.

You are affected if your EVlink charging station model matches one of the six listed models and is running firmware version r8_v3.4.0.1 or earlier, with the web server 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

Apply the vendor patch (R8 V3.4.0.1 or later) to all affected EVlink charging station models. If patching is not immediately feasible, implement network segmentation and restrict the charging station web server's outbound network access to prevent SSRF exploitation against internal systems.

Fix this in Evlink City Evc1s22p4 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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