dbcve.org
Evlink City Evc1s22p4 FirmwareOperating system · Schneider Electric

CVE-2021-22729

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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-259: Use of Hard-coded Password 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 gain unauthorized administrative privileges when accessing 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 hard-coded password vulnerability (CWE-259) exists in the web server of Schneider Electric EVlink charging stations (City, Parking, and Smart Wallbox models). The hard-coded administrative credentials allow attackers to bypass authentication and gain full administrative privileges on the charging station's web interface.

MitigationUpdate the firmware of affected EVlink charging stations to version R8 V3.4.0.1 or later, which removes the hard-coded credentials. If immediate patching is not possible, restrict network access to the charging station web servers to trusted networks only.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 model number label on the charging station or access the device's about/information page via the web interface. Confirm it is one of: Evc1s22p4, Evc1s7p4, Evw2, Evf2, Ev.2, or Evb1a.
    Affected if The model is any of the six listed affected models.
  2. Check the installed firmware version
    Access the charging station's web interface and navigate to the firmware or system information section. Alternatively, check the product label or documentation. Record the exact firmware version string.
    Affected if The firmware version is earlier than r8_v3.4.0.1 (for example, r8_v3.3.x or older).
  3. Verify web server accessibility
    Determine if the charging station's web interface is accessible over the network by attempting to reach the device IP on HTTP/HTTPS ports (typically 80/443 or configured ports). Check firewall or network segmentation settings.
    Affected if The web interface is network-accessible from untrusted networks.
  4. Confirm firmware version format
    Compare your recorded firmware version string against the vulnerable range. Look for version strings that start with 'r8_v' followed by a three-digit number lower than 3.4.0.1, such as r8_v3.3.0.0 or r8_v3.2.x.x.
    Affected if The firmware version begins with r8_v3 and the numeric portion is less than 3.4.0.1.

You are affected if your EVlink charging station model is one of the six listed models and the firmware version is older than r8_v3.4.0.1, with the web interface accessible on the network.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the firmware of affected EVlink charging stations to version R8 V3.4.0.1 or later, which removes the hard-coded credentials. If immediate patching is not possible, restrict network access to the charging station web servers to trusted networks only.

Recommended fix High confidence

R8 V3.4.0.1

  1. 1. Identify the specific EVlink product model (City EVC1S22P4, City EVC1S7P4, Parking EVW2, Parking EVF2, Parking EV.2, or Smart Wallbox EVB1A)
  2. 2. Access the device web interface or use the vendor's management tool to determine the current firmware version
  3. 3. Navigate to Schneider Electric's official download portal at download.schneider-electric.com
  4. 4. Locate and download the firmware version R8 V3.4.0.1 for your specific EVlink product model
  5. 5. Follow the official Schneider Electric firmware update procedure for your device (typically via the web interface under Administration > Firmware Update or similar)
  6. 6. After updating, verify the firmware version displays R8 V3.4.0.1 or later
  7. 7. Change any default credentials immediately after the update as a security best practice
Caveat Review Schneider Electric release notes for R8 V3.4.0.1 to confirm no loss of functionality for your specific use case

Generated from the published advisory — verify against the referenced sources before acting.

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-22729 — 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-22729 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