CVE-2021-22721
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-200: Information Exposure 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 get limited knowledge of javascript code 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 · moderate confidenceA CWE-200 Information Exposure vulnerability in Schneider Electric EVlink charging stations (City, Parking, and Smart Wallbox) allows attackers to obtain limited knowledge of JavaScript code by submitting crafted malicious parameters to the web server. The vulnerability exists in all versions prior to R8 V3.4.0.1.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the EVlink charging station modelLocate the product label on the charging station or access the web interface to identify the exact model number (Evc1s22p4, Evc1s7p4, Evw2, Evf2, Ev.2, or Evb1a)Affected if The model is any of the affected variants: City (Evc1s22p4, Evc1s7p4), Parking (Evw2, Evf2, Ev.2), or Smart Wallbox (Evb1a)
-
Check the installed firmware versionAccess the charging station web interface and navigate to the firmware information page, or use the manufacturer's diagnostic tool to retrieve the current firmware versionAffected if The firmware version is earlier than r8_v3.4.0.1 (for example, r8_v3.3.x or any version without the 3.4.0.1 update)
-
Verify the web server interface is enabledAttempt to access the charging station web interface by entering its IP address in a web browser, or check the network configuration settings to confirm the HTTP/HTTPS web server is activeAffected if The web server interface is accessible over the network (the vulnerability is exploited through crafted parameters submitted to this web server)
A user is affected if the EVlink charging station runs firmware versions prior to r8_v3.4.0.1 AND has the web server interface accessible on the network.
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.
From vendor dataUpgrade EVlink firmware to R8 V3.4.0.1 or later to patch the vulnerability. If immediate patching is not possible, restrict network access to the charging station web server interface to minimize attack surface.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22721 — 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-22721 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