dbcve.org
U.motion BuilderApplication · Schneider Electric

CVE-2018-7786

MEDIUM · 6.1 CVSS v3.0 Published 2018-07-03
Fix available
A fix is available. Upgrade to 1.3.4 or later.
See remediation →
68/100
Remediation priority · Elevated
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
In Schneider Electric U.motion Builder software versions prior to v1.3.4, a cross site scripting (XSS) vulnerability exists which could allow injection of malicious scripts.

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

Schneider Electric U.motion Builder versions prior to 1.3.4 contain a cross-site scripting (XSS) vulnerability in the web interface. Attackers can inject malicious JavaScript payloads through unsanitized user input fields, which then executes in the browsers of other users viewing the affected content.

MitigationUpgrade U.motion Builder to version 1.3.4 or later. If immediate patching is not possible, implement input validation and output encoding on all user-supplied data within the application.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 installed U.motion Builder version
    Locate the U.motion Builder installation and retrieve its version information through the application's interface, help menu, or installation directory documentation
    Affected if The installed version is any release prior to 1.3.4 (for example, 1.3.3, 1.3.0, 1.2.x)
  2. Confirm web interface is accessible
    Verify that the U.motion Builder web interface is reachable by accessing the application's HTTP/HTTPS endpoint in a browser or via network scan
    Affected if The web interface is exposed and accessible to users or attackers on the network
  3. Review input handling in web interface
    Examine user input fields within the U.motion Builder web interface for lack of input sanitization by submitting test payloads containing script tags
    Affected if User-supplied input is reflected back in responses without proper encoding, allowing injected JavaScript to execute

You are affected if U.motion Builder version is below 1.3.4 AND the web interface is accessible AND user input fields lack sanitization controls.

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. If immediate patching is not possible, implement input validation and output encoding on all user-supplied data within the application.

Fix this in U.motion Builder Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,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 $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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