# CVE-2025-2440: Information disclosure in Trio Q Licensed Data Radio

> A malicious user with physical access can expose confidential data by resetting the Trio Q Licensed Data Radio to factory defaults.

- **Severity:** Medium 4.1 (`CVSS:4.0/AV:P/AC:H/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Apr 2025
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-vv3m-5756-qf6f

## What is CVE-2025-2440?

CVE-2025-2440 is a medium-severity vulnerability in Schneider Electric Trio Q Licensed Data Radio, published on 9 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

CWE-922: Insecure Storage of Sensitive Information vulnerability exists that could potentially lead to unauthorized
access of confidential data when a malicious user, having physical access and advanced information on the file
system, sets the radio in factory default mode.

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

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


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

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

## Is CVE-2025-2440 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2440 is a medium-severity vulnerability in Schneider Electric Trio Q Licensed Data Radio, published on 9 Apr 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-2440 in the wild and no public exploit code.

Affected product: Schneider Electric Trio Q Licensed Data Radio. 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-2440/ (Markdown: https://insights.sbomify.com/CVE-2025-2440/index.md)
```

## Sources

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

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