# CVE-2025-10540: Unencrypted and Unauthenticated Communication Allows Data Exposure and Manipulation in iMonitor EAM

> Attackers can intercept and modify unencrypted traffic to steal sensitive data and issue commands in iMonitor EAM.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2025
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-2r7c-ggmc-xvcq

## What is CVE-2025-10540?

CVE-2025-10540 is a medium-severity vulnerability in iMonitor EAM, published on 25 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

iMonitor EAM 9.6394 transmits communication between the EAM client agent and the EAM server, as well as between the EAM monitor management software and the server, in plaintext without authentication or encryption. An attacker with network access can intercept sensitive information (such as credentials, keylogger data, and personally identifiable information) and tamper with traffic. This allows both unauthorized disclosure and modification of data, including issuing arbitrary commands to client agents.

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

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


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

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

## Is CVE-2025-10540 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10540 is a medium-severity vulnerability in iMonitor EAM, published on 25 Sep 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-10540 in the wild and no public exploit code.

Affected product: iMonitor EAM. 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-10540/ (Markdown: https://insights.sbomify.com/CVE-2025-10540/index.md)
```

## Sources

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

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