Skip to content
Fencer Intel
high 8.8

CVE-2018-7777 in the critical feed json

The vulnerability is due to insufficient handling of update_file request parameter on update_module.php in Schneider Electric U.motion Buil…

published 2018-07-03 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-19489

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
31.8%
EPSS 31.8% chance of exploitation in 30 days, percentile 98%
public exploits
1
Exploit-DB

Summary

The vulnerability is due to insufficient handling of update_file request parameter on update_module.php in Schneider Electric U.motion Builder software versions prior to v1.3.4. A remote, authenticated attacker can exploit this vulnerability by sending a crafted request to the target server.

Patch / fix

  • schneider-electric u.motion_builder 1.3.4

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-17-180-02 updated cvss 8.8

Schneider Electric U.motion Builder (Update A)

  • Schneider Electric Software, LLC U.motion Builder <= 1.2.1
    affected: vendor fix, mitigation “Schneider Electric's security notice SEVD-2017-178-01 is available” schneider-electric.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Timeline

  1. Published
  2. First public exploit (EDB-47991)

Exploit prediction

31.80% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-47991 Schneider Electric U.Motion Builder 1.3.4 - Authenticated Command Injection webapps, 2020-02-03

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P

Affected products

  • Schneider Electric SE U.Motion

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.