# CVE-2022-41671: SQL injection in EcoStruxure Operator Terminal Expert

> Local attackers can execute malicious SQL queries during project migration, leading to arbitrary code execution in Schneider Electric HMI software.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Nov 2022
- **Updated:** 1 May 2025
- **Also known as:** GHSA-jhfw-j77h-rvv3

## What is CVE-2022-41671?

CVE-2022-41671 is a high-severity SQL injection vulnerability in Schneider Electric EcoStruxure Operator Terminal Expert, published on 4 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A CWE-89: Improper Neutralization of Special Elements used in SQL Command (‘SQL Injection’) vulnerability exists that allows adversaries with local user privileges to craft a malicious SQL query and execute as part of project migration which could result in execution of malicious code. Affected Products: EcoStruxure Operator Terminal Expert(V3.3 Hotfix 1 or prior), Pro-face BLUE(V3.3 Hotfix1 or prior).

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2022-41671?

It affects 2 products.


Products: Schneider-Electric Ecostruxure Operator Terminal Expert, Schneider-Electric Pro-Face Blue.

## How do I fix CVE-2022-41671?

No fix has been published for CVE-2022-41671 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-41671 being exploited?

There is no known exploitation of CVE-2022-41671 in the wild and no public exploit code.

## Other vulnerabilities in Schneider Electric EcoStruxure Operator Terminal Expert

- [CVE-2020-28221](https://insights.sbomify.com/CVE-2020-28221/): Code injection in EcoStruxure™ Operator Terminal Expert 3.1 Service Pack 1A and prior running on Harmony HMIs HMIST6 Series, HMIG3U in HMIGTU Series, HMISTO Series and Pro-face BLUE 3.1 Service Pack 1A and prior running on Pro-face HMIs: ST6000 Series, SP-5B41 in SP5000 Series, GP4100 Series (critical 9.8)
- [CVE-2020-7497](https://insights.sbomify.com/CVE-2020-7497/): Path traversal in EcoStruxure Operator Terminal Expert 3.1 Service Pack 1 and prior (formerly known as Vijeo XD) (critical 9.8)
- [CVE-2023-1049](https://insights.sbomify.com/CVE-2023-1049/): Code injection in EcoStruxure™ Operator Terminal Expert (high 7.8)
- [CVE-2020-7493](https://insights.sbomify.com/CVE-2020-7493/): SQL injection in EcoStruxure Operator Terminal Expert 3.1 Service Pack 1 and prior (formerly known as Vijeo XD) (high 7.8)
- [CVE-2020-7494](https://insights.sbomify.com/CVE-2020-7494/): Path traversal in EcoStruxure Operator Terminal Expert 3.1 Service Pack 1 and prior (formerly known as Vijeo XD) (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41671 and fix it if it is affected.

What it is: CVE-2022-41671 is a high-severity SQL injection vulnerability in Schneider Electric EcoStruxure Operator Terminal Expert, published on 4 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-41671 in the wild and no public exploit code.

Affected product: Schneider Electric EcoStruxure Operator Terminal Expert. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-41671/ (Markdown: https://insights.sbomify.com/CVE-2022-41671/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41671
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41671
- OSV: https://osv.dev/vulnerability/CVE-2022-41671

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-41671/
Summaries are generated and may contain mistakes; the official description above is the record.