CVE-2021-22707
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 · uneditedA CWE-798: Use of Hard-coded Credentials 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 issue unauthorized commands to the charging station web server with administrative privileges.
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 confidenceHard-coded credentials are embedded in the web server of Schneider Electric EVlink charging stations (City, Parking, and Smart Wallbox models). An attacker with knowledge of these credentials can authenticate to the web interface with administrative privileges and issue unauthorized commands to the charging station.
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< r8_v3.4.0.1< r8_v3.4.0.1< r8_v3.4.0.1< r8_v3.4.0.1< r8_v3.4.0.1< r8_v3.4.0.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the EVlink charging station modelLocate the model number on the physical device label or access the web interface and look for the model identifier in the system information or status pageAffected if The model is one of: Evc1s22p4, Evc1s7p4, Evw2, Evf2, Ev.2, or Evb1a
-
Check the installed firmware versionAccess the charging station web interface and navigate to the firmware version, system information, or about page. Alternatively, check via the diagnostic port or maintenance interface if availableAffected if The firmware version is older than r8_v3.4.0.1 (for example, r8_v3.3.x or earlier)
-
Determine if the web interface is network-accessibleVerify network configuration to check if the charging station web interface port (typically HTTP/HTTPS on the device) is exposed to untrusted networks or the internetAffected if The web interface is reachable from untrusted networks or directly from the internet without network segmentation
-
Verify credential statusAttempt to log into the web interface with default administrative credentials, or review authentication logs if you have administrative accessAffected if The default administrative credentials are still active or have not been changed from factory defaults
-
Check for signs of unauthorized accessReview web server logs, authentication logs, or event logs on the charging station for unexpected administrative logins, unfamiliar IP addresses, or suspicious command activityAffected if There are log entries showing administrative logins from unknown IP addresses or commands issued by unknown accounts
You are affected if your charging station is one of the listed models AND runs firmware older than r8_v3.4.0.1 AND the web interface is accessible to potential attackers with the hard-coded credentials.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate all affected EVlink charging station firmware to R8 V3.4.0.1 or later, and change any default administrative passwords to unique, strong credentials.
R8 V3.4.0.1
- Identify the specific EVlink model (City EVC1S22P4, City EVC1S7P4, Parking EVW2, Parking EVF2, Parking EV.2, or Smart Wallbox EVB1A) that needs remediation
- Access the Schneider Electric download portal at download.schneider-electric.com
- Locate the firmware update for your specific EVlink model
- Download firmware version r8_v3.4.0.1 or later for your device
- Follow Schneider Electric's official firmware upgrade procedure for your specific model
- Verify the firmware has been successfully updated to r8_v3.4.0.1 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22707 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-22707 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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