Threats / Schneider Electric / CVE-2018-7841
CVE-2018-7841
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Schneider Electric U.motion Builder vulnerability
SQL Injection vulnerability in Schneider Electric U.motion Builder allows remote code execution through malformed input.
Verdict
Today item — known-exploited.
A SQL Injection flaw (CWE-89) in U.motion Builder enables attackers to execute arbitrary code by injecting malicious SQL commands. The vulnerability has been observed in active exploitation in the wild.
CISA KEV Yes · 2022-04-154EPSS 0.72675 (verify live)5CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3Exploit Public PoC / detection · nuclei template11
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
126 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-04-15).
Probability (EPSS)
EPSS 0.72675 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Schneider Electric, U.motion Builder. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-89 SQL Injection — weakness family: Injection.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1059 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft SQL injection payloads and submit them through U.motion Builder input fields to bypass authentication or extract data.
Business
Unauthorized access to sensitive configuration data and operational technology systems managed by U.motion Builder.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I escalate the SQL injection to achieve remote code execution on the underlying database or application server.
Business
Complete compromise of the U.motion Builder platform and potential lateral movement into critical industrial control infrastructure.
3
Lateral reach — past segmentation narrative 3
Attacker
I maintain persistent access by establishing backdoors or creating privileged accounts within the compromised system.
Business
Long-term operational disruption, data theft, and loss of control over automation and building management systems.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05