# CVE-2025-2002: Information disclosure in EcoStruxure Panel Server

> Administrators enabling debug mode may expose FTP credentials in exported logs, requiring careful log management to prevent credential theft.

- **Severity:** Medium 4.0 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2025
- **Updated:** 12 May 2025
- **Also known as:** GHSA-jrp2-pgjj-vwpm

## What is CVE-2025-2002?

CVE-2025-2002 is a medium-severity vulnerability in Schneider Electric EcoStruxure Panel Server, published on 12 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

CWE-532: Insertion of Sensitive Information into Log Files vulnerability exists that could cause the disclosure
of FTP server credentials when the FTP server is deployed, and the device is placed in debug mode by an
administrative user and the debug files are exported from the device.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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


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

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

## Is CVE-2025-2002 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2002 is a medium-severity vulnerability in Schneider Electric EcoStruxure Panel Server, published on 12 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2002 in the wild and no public exploit code.

Affected product: Schneider Electric EcoStruxure Panel Server. 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-2002/ (Markdown: https://insights.sbomify.com/CVE-2025-2002/index.md)
```

## Sources

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

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