Schneider Electric
EVlink Home Smart
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2024-8070 | 13 Oct 2024 | All versions prior to 2.0.6.0.0; All versions prior to 1.13.4 | For already connected products, version 2.0.6.0.0 of EVlink Home Smart includes a fix for this vulnerability and has been deployed to automatically upgrade all charging stations connected to the Wiser application. Make sure the charging station is connected to the Wiser application to ensure the new version is downloaded and installed. For new installations, a fix for this vulnerability is enforced through eSetup commissioning application. The installed firmware version can be verified through Wiser application (refer to the settings page for the charging station). | Update reference ↗ |
| CVE-2024-5313 | 12 Jun 2024 | v2.0.4.1.2_131; v2.0.3.8.2_128 | Version 2.0.5.0.0_134 of EVlink Home Smart includes a fix for this vulnerability that has been automatically deployed since April 19th to all charging stations connected to the Wiser application. Make sure the charging station is connected to the Wiser application to ensure the new version can be downloaded and installed. The installed firmware version can be verified through Wiser application (refer to the settings page for the charging station). | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.