dbcve.org
U.motion BuilderApplication · Schneider Electric

CVE-2018-7769

HIGH · 8.8 CVSS v3.0 Published 2018-07-03
Fix available
A fix is available. Upgrade to 1.3.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
The vulnerability exists within processing of xmlserver.php in Schneider Electric U.motion Builder software versions prior to v1.3.4. The underlying SQLite database query is subject to SQL injection on the id input parameter.

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 · high confidence

SQL injection vulnerability in Schneider Electric U.motion Builder xmlserver.php where the 'id' input parameter is not sanitized before being used in an SQLite database query, allowing arbitrary SQL command execution.

MitigationUpgrade U.motion Builder to version 1.3.4 or later which contains the patched code, or implement input validation/sanitization on the id parameter if upgrading is not feasible.

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
U.motion BuilderApplication
Affected:< 1.3.4

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/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. Identify if U.motion Builder is installed
    Look for the U.motion Builder installation directory, typically found in C:\Program Files\Schneider Electric\U.motion Builder or C:\Program Files (x86)\Schneider Electric\U.motion Builder on Windows systems. Check for the presence of the xmlserver.php file within the installation.
    Affected if The software is present on the system but the version cannot be determined or is confirmed to be below 1.3.4
  2. Determine the installed version of U.motion Builder
    Locate the version information in the installation directory, typically in a version.txt, about dialog, or the installer log files. The version may also be visible in the software's help or about section if the application can be launched.
    Affected if The installed version is anything less than 1.3.4, or if version information cannot be located and the software is present
  3. Locate the vulnerable xmlserver.php file
    Search for xmlserver.php within the U.motion Builder installation directory, particularly in web server related subfolders such as www, htdocs, web, or similar directories that serve the web interface.
    Affected if The xmlserver.php file exists in the installation and the software version is below 1.3.4
  4. Verify web interface accessibility
    Determine if the U.motion Builder web interface is exposed or accessible. Check if the web server component is running and if network listeners are configured for the application.
    Affected if The web interface is accessible and the U.motion Builder version is below 1.3.4, making the SQL injection exploitable remotely if the id parameter is accepted
  5. Check for presence of the id parameter in xmlserver.php
    Examine the xmlserver.php source code if accessible, looking for the id parameter usage within database queries. Look for SQL statements that directly incorporate the id parameter without visible sanitization or parameterized queries.
    Affected if The source code shows direct use of the id parameter in SQL queries without sanitization, and the version is below 1.3.4

A user is affected if Schneider Electric U.motion Builder is installed with a version lower than 1.3.4 and the xmlserver.php component is present and accessible.

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.

From vendor data
Upgrade available Upgrade to 1.3.4 or later
Fixed in 1.3.4
Interim mitigation

Upgrade U.motion Builder to version 1.3.4 or later which contains the patched code, or implement input validation/sanitization on the id parameter if upgrading is not feasible.

Fix this in U.motion Builder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,200
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,520.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-7769 — 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-2018-7769 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