Command execution via malicious project file processing
Published Mar 10, 2026 · Updated Mar 10, 2026
Code injection in Schneider Electric EcoStruxure Automation Expert before 25.0.1 allows local users to run commands via a malicious project file. Schneider Electric has not disclosed which project-file parser or operation converts attacker-controlled project content into executable commands. Exploitation requires an authenticated user to open the file on a Windows engineering workstation, enabling compromise of that workstation and subsequent systems.
Summary
What happened
Code injection in Schneider Electric EcoStruxure Automation Expert before 25.0.1 allows local users to run commands via a malicious project file. Schneider Electric has not disclosed which project-file parser or operation converts attacker-controlled project content into executable commands. Exploitation requires an authenticated user to open the file on a Windows engineering workstation, enabling compromise of that workstation and subsequent systems.
The record
- CVE
- CVE-2026-2273
- Published
- Mar 10, 2026
- Updated
- Mar 10, 2026
- Vendor
- Distributed Data Systems
- Product
- EcoStruxure Automation Expert
- Classifications
- CWE-94, T1204.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 10, 2026CVE publishedPublication date reported by the CVE source.
- Mar 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Versions prior to v25.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo