# CVE-2025-6788: Information disclosure in EcoStruxure™ Power Monitoring Expert

> Authenticated users can access TGML diagram resources they should not see, leading to unauthorized information disclosure in Schneider Electric power monitoring systems.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 11 Jul 2025
- **Updated:** 22 Jul 2025
- **Also known as:** GHSA-q2rf-262f-hfr2

## What is CVE-2025-6788?

CVE-2025-6788 is a medium-severity vulnerability in Schneider Electric EcoStruxure™ Power Monitoring Expert, published on 11 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A CWE-668: Exposure of Resource to Wrong Sphere vulnerability exists that exposes TGML diagram resources
to the wrong control sphere, providing other authenticated users with potentially inappropriate access to TGML
diagrams.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

## Which versions are affected by CVE-2025-6788?


## How do I fix CVE-2025-6788?

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

## Is CVE-2025-6788 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6788 and fix it if it is affected.

What it is: CVE-2025-6788 is a medium-severity vulnerability in Schneider Electric EcoStruxure™ Power Monitoring Expert, published on 11 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-6788 in the wild and no public exploit code.

Affected product: Schneider Electric EcoStruxure™ Power Monitoring Expert. 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-2025-6788/ (Markdown: https://insights.sbomify.com/CVE-2025-6788/index.md)
```

## Sources

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

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