CVE-2018-7770
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 sendmail.php in Schneider Electric U.motion Builder software versions prior to v1.3.4. The applet allows callers to select arbitrary files to send to an arbitrary email address.
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 confidenceThe sendmail.php applet in Schneider Electric U.motion Builder (versions prior to v1.3.4) contains an arbitrary file read and email sending vulnerability. Attackers can specify any accessible file on the system to be attached and sent to any email address of their choosing, enabling sensitive data exfiltration and abuse of the server as a spam relay.
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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify U.motion Builder installation and versionLocate the U.motion Builder installation directory and check the version information, typically found in the application metadata, installer properties, or about/version file within the product directory.Affected if Installed version is prior to 1.3.4 (e.g., 1.3.3, 1.3.2, 1.2.x, etc.)
-
Locate the sendmail.php fileSearch the U.motion Builder web directory for the sendmail.php file, which is the vulnerable applet mentioned in the CVE.Affected if The sendmail.php file exists in the web-accessible directory (e.g., /web/sendmail.php or similar path under the installation root).
-
Verify web interface accessibilityDetermine if the U.motion Builder web interface (HTTP/HTTPS) is reachable from the network. Check firewall rules, network bindings, and web server configuration.Affected if The web interface is exposed to network access without proper access controls.
-
Check for suspicious email activityReview email server logs, mail queues, or SMTP traffic for unexpected or unauthorized email messages originating from the U.motion Builder server, particularly with attachments.Affected if Unexpected email messages with arbitrary file attachments are being sent from the server to external addresses.
You are affected if U.motion Builder version is below 1.3.4 AND the sendmail.php applet is accessible on your network.
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, which contains the fix for this vulnerability. If immediate patching is not possible, restrict network access to the affected interface and monitor for suspicious email traffic.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7770 — 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-7770 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