# CVE-2025-10542: Insecure Default Admin Credentials Enable Full Administrative Access in iMonitor EAM

> Remote attackers can use default admin credentials to access iMonitor EAM, read sensitive telemetry, and control monitored agents.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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-35hw-x784-33fr

## What is CVE-2025-10542?

CVE-2025-10542 is a critical 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 ships with default administrative credentials that are also displayed within the management client’s connection dialog. If the administrator does not change these defaults, a remote attacker can authenticate to the EAM server and gain full control over monitored agents and data. This enables reading highly sensitive telemetry (including keylogger output) and issuing arbitrary actions to all connected clients.

Weakness: CWE-1392 (Use of Default Credentials)

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


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

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

## Is CVE-2025-10542 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10542 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10542 is a critical 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10542 exists.

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-10542/ (Markdown: https://insights.sbomify.com/CVE-2025-10542/index.md)
```

## Sources

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

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