CVE-2018-7765
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 · uneditedThe vulnerability exists within processing of track_import_export.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 object_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 confidenceSQL injection vulnerability in Schneider Electric U.motion Builder prior to v1.3.4 allows remote attackers to manipulate SQLite database queries via the object_id parameter in track_import_export.php.
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< 1.3.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm U.motion Builder is installedLocate the U.motion Builder installation directory. Check common paths such as C:\Program Files\Schneider Electric\U.motion Builder or /opt/umotion builder, or search for files named 'track_import_export.php' on the system.Affected if U.motion Builder software is not present on the system.
-
Identify installed versionOpen the U.motion Builder application and navigate to Help > About, or check for a version file in the installation directory such as version.txt, or examine the application's main executable metadata.Affected if The version cannot be determined or is lower than 1.3.4.
-
Verify vulnerable file existsSearch for the file track_import_export.php within the web server root or U.motion Builder installation directories, typically under a 'php' or 'web' subdirectory.Affected if The file track_import_export.php exists on the system.
-
Check if web interface is exposedVerify whether the U.motion Builder web server is running and accessible. Check if ports 80, 443, or the configured web port are open and responding. Review network firewall rules or router configurations for port exposures.Affected if The web interface is accessible from the network.
-
Confirm object_id parameter acceptanceIf the web interface is accessible, inspect the track_import_export.php file or attempt a test request to the endpoint to confirm it accepts the object_id parameter.Affected if The endpoint accepts user-supplied input via the object_id parameter without sanitization.
If U.motion Builder is installed with a version lower than 1.3.4 and the track_import_export.php file exists with an exposed web interface, the environment is affected by CVE-2018-7765.
Generated from the published advisory. Verify against your own configuration.
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 data1.3.4
Upgrade to U.motion Builder v1.3.4 or later, or implement parameterized queries/input validation on the object_id parameter to prevent SQL injection.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2018-7765 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-7765 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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