# CVE-2018-7841: Schneider Electric U.motion Builder SQL Injection

> SQL injection in U.motion Builder allows attackers to execute unwanted code via improper character input.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 15 Apr 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 May 2019
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-cwjr-6hc3-vpjm

## What is CVE-2018-7841?

CVE-2018-7841 is a critical SQL injection vulnerability in U.motion Builder software version 1.3.4, published on 22 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A SQL Injection (CWE-89) vulnerability exists in U.motion Builder software version 1.3.4 which could cause unwanted code execution when an improper set of characters is entered.

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

## Which versions are affected by CVE-2018-7841?

It affects 1 product.


Products: Schneider-Electric U.motion Builder.

## How do I fix CVE-2018-7841?

No fix has been published for CVE-2018-7841 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 6 May 2022.

## Is CVE-2018-7841 being exploited?

Yes. Attackers have exploited CVE-2018-7841 in the wild since at least 15 Apr 2022.

Public exploit code:

- Schneider Electric U.Motion Builder 1.3.4 - 'track_import_export.php object_id' Unauthenticated Command Injection (exploitdb)
- Schneider Electric U.motion Builder - Remote Code Execution (nuclei): http/cves/2018/CVE-2018-7841.yaml

## Other vulnerabilities in U.motion Builder software version 1.3.4

- [CVE-2018-7785](https://insights.sbomify.com/CVE-2018-7785/): Command injection in U.motion Builder (critical 9.8)
- [CVE-2017-7973](https://insights.sbomify.com/CVE-2017-7973/): SQL injection in U.Motion (critical 9.8)
- [CVE-2017-7974](https://insights.sbomify.com/CVE-2017-7974/): Path traversal in U.Motion (critical 9.8)
- [CVE-2017-9957](https://insights.sbomify.com/CVE-2017-9957/): Hardcoded credentials in U.Motion (critical 9.8)
- [CVE-2018-7765](https://insights.sbomify.com/CVE-2018-7765/): SQL injection in U.Motion (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7841 and fix it if it is affected.

What it is: CVE-2018-7841 is a critical SQL injection vulnerability in U.motion Builder software version 1.3.4, published on 22 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2018-7841 in the wild since at least 15 Apr 2022.

Affected product: U.motion Builder software version 1.3.4. 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-2018-7841/ (Markdown: https://insights.sbomify.com/CVE-2018-7841/index.md)
```

## Sources

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

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