# CVE-2020-7547: Privilege escalation in EcoStruxureª and SmartStruxureª Power Monitoring and SCADA Software (see security notification for version information)

> Attackers can perform unauthorized actions at higher privilege levels via the web interface of Schneider Electric SCADA software.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-c5c3-mf59-3rh5

## What is CVE-2020-7547?

CVE-2020-7547 is a high-severity vulnerability in EcoStruxureª and SmartStruxureª Power Monitoring and SCADA Software (see security notification for version information), published on 1 Dec 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A CWE-284: Improper Access Control vulnerability exists in EcoStruxureª and SmartStruxureª Power Monitoring and SCADA Software (see security notification for version information) that could allow a user the ability to perform actions via the web interface at a higher privilege level.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2020-7547?

It affects 5 products.


Products: Schneider-Electric Ecostruxure Energy Expert, Schneider-Electric Ecostruxure Power Monitoring Expert, Schneider-Electric Power Manager, Schneider-Electric Powerscada Expert With Advanced Reporting and Dashboards, Schneider-Electric Powerscada Operation With Advanced Reporting and Dashboards.

## How do I fix CVE-2020-7547?

No fix has been published for CVE-2020-7547 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-7547 being exploited?

There is no known exploitation of CVE-2020-7547 in the wild and no public exploit code.

## Other vulnerabilities in EcoStruxureª and SmartStruxureª Power Monitoring and SCADA Software (see security notification for version information)

- [CVE-2020-7545](https://insights.sbomify.com/CVE-2020-7545/): Missing authorization in EcoStruxureª and SmartStruxureª Power Monitoring and SCADA Software (see security notification for version information) (high 7.2)
- [CVE-2018-7797](https://insights.sbomify.com/CVE-2018-7797/): Open redirect 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 (medium 6.1)
- [CVE-2020-7546](https://insights.sbomify.com/CVE-2020-7546/): Cross-site scripting in EcoStruxureª and SmartStruxureª Power Monitoring and SCADA Software (see security notification for version information) (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-7547 and fix it if it is affected.

What it is: CVE-2020-7547 is a high-severity vulnerability in EcoStruxureª and SmartStruxureª Power Monitoring and SCADA Software (see security notification for version information), published on 1 Dec 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-7547 in the wild and no public exploit code.

Affected product: EcoStruxureª and SmartStruxureª Power Monitoring and SCADA Software (see security notification for version information). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-7547/ (Markdown: https://insights.sbomify.com/CVE-2020-7547/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-7547
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-7547
- OSV: https://osv.dev/vulnerability/CVE-2020-7547

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-7547/
Summaries are generated and may contain mistakes; the official description above is the record.