dbcve.org
Ecostruxure Energy ExpertApplication · Schneider Electric

CVE-2018-7797

MEDIUM · 6.1 CVSS v3.0 Published 2018-12-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A URL redirection vulnerability exists in Power Monitoring Expert, Energy Expert (formerly Power Manager) - EcoStruxure Power Monitoring Expert (PME) v8.2 (all editions), EcoStruxure Energy Expert 1.3 (formerly Power Manager), EcoStruxure Power SCADA Operation (PSO) 8.2 Advanced Reports and Dashboards Module, EcoStruxure Power Monitoring Expert (PME) v9.0, EcoStruxure Energy Expert v2.0, and EcoStruxure Power SCADA Operation (PSO) 9.0 Advanced Reports and Dashboards Module which could cause a phishing attack when redirected to a malicious site.

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 · moderate confidence

Open redirect vulnerability in multiple EcoStruxure Power Monitoring and SCADA products allows attackers to craft malicious URLs that redirect users to phishing sites. The vulnerability exists in the Advanced Reports and Dashboards modules across versions 8.2 and 9.0, where user-supplied input in redirect parameters is not properly validated before forwarding users.

MitigationImplement strict allowlist-based validation for redirect URLs, ensuring only internal relative paths are permitted and rejecting any user-controlled external URLs. Alternatively, remove user-controllable redirect parameters entirely or use server-side mapping of safe redirect destinations.

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
Ecostruxure Energy ExpertApplication
Affected:= 1.3= 2.0
Ecostruxure Power Monitoring ExpertApplication
Affected:= 8.2= 9.0
Ecostruxure Power Scada OperationApplication
Affected:= 8.2= 9.0

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 the installed EcoStruxure product
    Check the product name displayed in the application interface, login page, or installed software list on the system. Schneider Electric EcoStruxure products include Energy Expert, Power Monitoring Expert, and Power Scada Operation.
    Affected if The product is EcoStruxure Energy Expert, Power Monitoring Expert, or Power Scada Operation
  2. Determine the installed product version
    Locate the version information in the application (typically in Help > About, the installer, or the product's control panel). Compare the version number against the affected ranges: 1.3, 2.0, 8.2, or 9.0.
    Affected if The installed version matches exactly 1.3, 2.0, 8.2, or 9.0
  3. Verify if Advanced Reports or Dashboards module is accessible
    Log into the web interface and navigate to the Advanced Reports or Dashboards module. These modules are part of the web-based reporting and visualization features of the affected products.
    Affected if The Advanced Reports or Dashboards module is accessible and enabled in the installation
  4. Inspect web access logs for redirect parameter patterns
    Review the application's web server logs (typically found in the product's log directory) for requests containing redirect, url, dest, next, or similar parameters pointing to external domains. Example suspicious patterns: ?redirect=http://, ?url=https://, ?dest=//example.com
    Affected if Log entries show redirect parameters with external or unexpected URLs being processed by the web application

A user is affected if they run any of the three EcoStruxure products at versions 1.3, 2.0, 8.2, or 9.0 and have the Advanced Reports or Dashboards module enabled and accessible via the web interface.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict allowlist-based validation for redirect URLs, ensuring only internal relative paths are permitted and rejecting any user-controlled external URLs. Alternatively, remove user-controllable redirect parameters entirely or use server-side mapping of safe redirect destinations.

Fix this in Ecostruxure Energy Expert Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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