CVE-2021-22730
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 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 confidenceHard-coded credentials are embedded in the web server of EVlink City, EVlink Parking, and EVlink Smart Wallbox charging stations. Attackers can use these credentials to gain unauthorized administrative access to the charging station web interfaces, bypassing authentication entirely.
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 charging station modelLocate the product model label on the physical device or check the device configuration. Confirm it is one of: Evlink City Evc1s22p4, Evlink City Evc1s7p4, Evlink Parking Evw2, Evlink Parking Evf2, Evlink Parking Ev.2, or Evlink Smart Wallbox Evb1aAffected if The model matches any of the listed affected products and the firmware version is below r8_v3.4.0.1
-
Check the installed firmware versionAccess the device web interface or use the vendor management tool to view the firmware version information. Compare the version string to r8_v3.4.0.1Affected if The firmware version begins with a number lower than r8_v3.4.0.1, or shows a version that does not start with r8_v3.4.0.1 or higher
-
Verify web server accessibilityAttempt to access the device web interface by entering the device IP address in a web browser. Check if the login page loads successfullyAffected if The web interface is reachable on the network and displays a login prompt
-
Test for hard-coded credential accessUse the documented hard-coded credentials (if known) or attempt to access administrative functions without valid user credentials. Look for successful authentication bypass or unauthorized admin accessAffected if Authentication can be bypassed or administrative access is gained without valid credentials, indicating the hard-coded credentials are present
The environment is affected if the charging station model is one of the listed products and the firmware version is below r8_v3.4.0.1, with the web interface accessible for exploitation.
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 charging stations to firmware version R8 V3.4.0.1 or later, which removes the hard-coded credentials and implements proper authentication mechanisms.
r8_v3.4.0.1
- 1. Navigate to the Schneider Electric download portal at download.schneider-electric.com
- 2. Locate the firmware download section for your specific EVlink product model (EVC1S22P4, EVC1S7P4, EVW2, EVF2, EV.2, or EVB1A)
- 3. Download the firmware version r8_v3.4.0.1 or later for your device
- 4. Access the charging station's web interface using administrative credentials
- 5. Navigate to the firmware update or system settings section
- 6. Upload and apply the new firmware file
- 7. Verify the firmware installation was successful by checking the firmware version displayed in the web interface
- 8. Change any default administrative credentials immediately after the upgrade to further harden the device
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-22730 — 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-22730 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