# CVE-2025-1060: Information disclosure in ASCO 5310 Single-Channel Remote Annunciator

> Attackers can sniff network traffic to expose sensitive data transmitted in cleartext by Schneider Electric remote annunciators.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2025
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-v7c4-4678-h94w

## What is CVE-2025-1060?

CVE-2025-1060 is a high-severity vulnerability in Schneider Electric ASCO 5310 Single-Channel Remote Annunciator, published on 13 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CWE-319: Cleartext Transmission of Sensitive Information vulnerability exists that could result in the exposure
of data when network traffic is being sniffed by an attacker.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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


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

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

## Is CVE-2025-1060 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1060 is a high-severity vulnerability in Schneider Electric ASCO 5310 Single-Channel Remote Annunciator, published on 13 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1060 in the wild and no public exploit code.

Affected product: Schneider Electric ASCO 5310 Single-Channel Remote Annunciator. 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-1060/ (Markdown: https://insights.sbomify.com/CVE-2025-1060/index.md)
```

## Sources

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

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