dbcve.org
Ecostruxure Automation ExpertApplication · Schneider Electric

CVE-2026-2273

HIGH · 8.2 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 25.0.1 or later.
See remediation →
82/100
Remediation priority · High

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 · unedited
CWE-94: Improper Control of Generation of Code ('Code Injection') vulnerability exist that could cause execution of untrusted commands on the engineering workstation which could result in a limited compromise of the workstation and a potential loss of Confidentiality, Integrity and Availability of the subsequent system when an authenticated user opens a malicious project file.

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 confidence

A CWE-94 code injection vulnerability exists in software that handles project files on engineering workstations. When an authenticated user opens a specially crafted malicious project file, the software improperly handles data within the file leading to execution of untrusted commands, compromising the workstation.

MitigationImplement strict input validation and sanitization when parsing project files to prevent code injection. Consider using safelisting for allowed characters/patterns and avoid dynamic code execution functions. Restrict file parsing privileges where possible.

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
Ecostruxure Automation ExpertApplication
Affected:< 25.0.1

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify if Schneider Electric Ecostruxure Automation Expert is installed
    Check for the application in the system program files or look for its executable (typically in Program Files/Schneider Electric or similar). On Windows, review installed programs via Control Panel > Programs and Features, or use PowerShell: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Ecostruxure*Automation*Expert*'}
    Affected if The application is present on the system
  2. Determine the installed version number
    Locate the application's version information. This is typically available in the application's about dialog, executable properties (right-click the .exe file > Properties > Details), or in the Windows registry under the uninstall key for the product. Compare the version to 25.0.1.
    Affected if The installed version is lower than 25.0.1 (for example, 24.x.x, 23.x.x, etc.)
  3. Confirm the user has authenticated access to the application
    Verify that the user account in question has valid credentials or permissions to log into the Ecostruxure Automation Expert application. The vulnerability requires an authenticated user to open a malicious project file.
    Affected if The user can authenticate and access the application with privileges to open or import project files
  4. Check if project file operations are available
    Determine if the installation includes the project file parsing module and whether users can open, import, or load project files (.eaedx, .xml, or other project file formats used by the software). This is the attack vector for the vulnerability.
    Affected if Project file opening/import functionality is accessible to the authenticated user

A user is affected if Schneider Electric Ecostruxure Automation Expert is installed with a version below 25.0.1 and the user has authenticated access to open or import project files, as the command injection occurs through the project file parser.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 25.0.1 or later
Fixed in 25.0.1
Interim mitigation

Implement strict input validation and sanitization when parsing project files to prevent code injection. Consider using safelisting for allowed characters/patterns and avoid dynamic code execution functions. Restrict file parsing privileges where possible.

Recommended fix High confidence

Ecostruxure Automation Expert 25.0.1

  1. Identify the current version of Ecostruxure Automation Expert installed on the engineering workstation
  2. Navigate to the official Schneider Electric download portal at download.schneider-electric.com
  3. Locate and download Ecostruxure Automation Expert version 25.0.1 or later
  4. Follow the vendor's standard upgrade procedure to apply the update to the engineering workstation
  5. After upgrading, verify the installed version is 25.0.1 or higher to confirm the patch was applied

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ecostruxure Automation Expert Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2273 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2273 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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