# CVE-2025-22495: Command injection in Network M2

> Authenticated high-privileged users can execute arbitrary commands via improper input validation in the NTP configuration of the end-of-life Network-M2 card.

- **Severity:** High 8.4 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Feb 2025
- **Updated:** 26 Aug 2025
- **Also known as:** GHSA-pjqh-q2j4-8c7q

## What is CVE-2025-22495?

CVE-2025-22495 is a high-severity command injection vulnerability in Eaton Network M2, published on 24 Feb 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

An improper input validation vulnerability was discovered in the NTP server configuration field of the Network-M2 card. This could result in an authenticated high privileged user having the ability to execute arbitrary commands. The vulnerability has been resolved in the version 3.0.4. 
Note - Network-M2 has been declared end-of-life in early 2024 and Network-M3 has been released as a fit-and-functional replacement.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2025-22495 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-22495 is a high-severity command injection vulnerability in Eaton Network M2, published on 24 Feb 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-22495 in the wild and no public exploit code.

Affected product: Eaton Network M2. 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-22495/ (Markdown: https://insights.sbomify.com/CVE-2025-22495/index.md)
```

## Sources

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

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