Schneider Electric
EcoStruxure Process Expert
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-2025-0327 | 13 Feb 2025 | Versions 2020R2; Versions 2021 & 2023 (prior to v4.8.0.5715); Versions 2021 & 2023 | Version v4.8.0.5715 of EcoStruxure™ Process Expert 2023 Software Package includes a fix for this vulnerability and is available for download here: https://www.se.com/ww/en/product-range/65406-ecostruxure-processexpert/#software-and-firmware Uninstall Previous Version 2023 (v4.8.0.5115) before installing Version 2023 (v4.8.0.5715). Version string could be found on engineering server console. | Update reference ↗ |
| CVE-2022-24323 | 9 Mar 2022 | V2021 and prior; V15.0 SP1 and prior | Version 15.1 of EcoStruxure™ Control Expert includes a fix for these vulnerabilities and is available for download here: https://www.se.com/ww/en/download/document/EcoStruxureControlExpert_V15.1/ Customers using Unity Pro should strongly consider migrating to EcoStruxure™ Control Expert. If customers choose not to apply the remediation provided above, they should immediately apply the following mitigations to reduce the risk of exploit: To mitigate the risks associated to Modbus weaknesses, users should immediately: • Setup network segmentation and implement a firewall to block all unauthorized access to port 502/TCP | 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.