CVE-2021-22727: A CWE-331: Insufficient Entropy vulnerability exists in EVlink City (EVC1S22P4 / EVC1S7P4 all versions prior to R8 V3.4.0.1), EVlink Parking…
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.4% (FIRST EPSS); higher than 72.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A CWE-331: Insufficient Entropy 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 access to the charging station web server
- Published
- Jul 21, 2021
- Updated
- Jun 16, 2026
- EPSS
- 1.4% · 72th percentile
- CWE
- CWE-331
Report tools
Action score
39
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| schneider-electric | evlink city evc1s22p4 firmware | cpe:2.3:o:schneider-electric:evlink_city_evc1s22p4_firmware |
| schneider-electric | evlink city evc1s22p4 | cpe:2.3:h:schneider-electric:evlink_city_evc1s22p4 |
| schneider-electric | evlink city evc1s7p4 firmware | cpe:2.3:o:schneider-electric:evlink_city_evc1s7p4_firmware |
| schneider-electric | evlink city evc1s7p4 | cpe:2.3:h:schneider-electric:evlink_city_evc1s7p4 |
| schneider-electric | evlink parking evw2 firmware | cpe:2.3:o:schneider-electric:evlink_parking_evw2_firmware |
| schneider-electric | evlink parking evw2 | cpe:2.3:h:schneider-electric:evlink_parking_evw2 |
| schneider-electric | evlink parking evf2 firmware | cpe:2.3:o:schneider-electric:evlink_parking_evf2_firmware |
| schneider-electric | evlink parking evf2 | cpe:2.3:h:schneider-electric:evlink_parking_evf2 |
| schneider-electric | evlink parking ev.2 firmware | cpe:2.3:o:schneider-electric:evlink_parking_ev.2_firmware |
| schneider-electric | evlink parking ev.2 | cpe:2.3:h:schneider-electric:evlink_parking_ev.2 |
| schneider-electric | evlink smart wallbox evb1a firmware | cpe:2.3:o:schneider-electric:evlink_smart_wallbox_evb1a_firmware |
| schneider-electric | evlink smart wallbox evb1a | cpe:2.3:h:schneider-electric:evlink_smart_wallbox_evb1a |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (schneider). Independent of NVD's CPE analysis and usually ahead of it.
n/a 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
- 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 V3affected
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- schneider-electric evlink city evc1s22p4 firmwarebefore r8_v3.4.0.1
- schneider-electric evlink city evc1s7p4 firmwarebefore r8_v3.4.0.1
- schneider-electric evlink parking ev.2 firmwarebefore r8_v3.4.0.1
- schneider-electric evlink parking evf2 firmwarebefore r8_v3.4.0.1
- schneider-electric evlink parking evw2 firmwarebefore r8_v3.4.0.1
- schneider-electric evlink smart wallbox evb1a firmwarebefore r8_v3.4.0.1
Same product
schneider-electric: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-22707A CWE-798: Use of Hard-coded Credentials vulnerability exists in EVlink City (EVC1S22P4 / EVC1S7P4 all versions prior to R8 V3.4.0.1)…58Plan
- CVE-2021-22729A CWE-259: Use of Hard-coded Password vulnerability exists in EVlink City (EVC1S22P4 / EVC1S7P4 all versions prior to R8 V3.4.0.1), EVlink…40Plan
- CVE-2021-22820A CWE-614 Insufficient Session Expiration vulnerability exists that could allow an attacker to maintain an unauthorized access over a…39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-22723Jul 21, 2021 · A CWE-79: Improper Neutralization of Input During Web Page Generation (Cross-siteScripting) through Cross-Site Request Forgery (CSRF)…24Monitor
- ← EarlierCVE-2021-22726Jul 21, 2021 · A CWE-918: Server-Side Request Forgery (SSRF) vulnerability exists in EVlink City (EVC1S22P4 / EVC1S7P4 all versions prior to R8 V3.4.0.1)…32Monitor
- Later →CVE-2021-22728Jul 21, 2021 · A CWE-200: Information Exposure vulnerability exists in EVlink City (EVC1S22P4 / EVC1S7P4 all versions prior to R8 V3.4.0.1), EVlink…26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-331 · Insufficient EntropyCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.