# CVE-2025-41721: Sauter: Command Injection

> A high-privileged remote attacker can execute arbitrary commands via improper input validation in the certificate management feature of Sauter building automation devices.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Oct 2025
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-qg9r-fg3h-59p8

## What is CVE-2025-41721?

CVE-2025-41721 is a low-severity command injection vulnerability in Sauter EY-modulo 5 ecos 5 ecos504/505, published on 22 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A high privileged remote attacker can influence the parameters passed to the openssl command due to improper neutralization of special elements when adding a password protected self-signed certificate.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2025-41721 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41721 is a low-severity command injection vulnerability in Sauter EY-modulo 5 ecos 5 ecos504/505, published on 22 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-41721 in the wild and no public exploit code.

Affected product: Sauter EY-modulo 5 ecos 5 ecos504/505. 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-41721/ (Markdown: https://insights.sbomify.com/CVE-2025-41721/index.md)
```

## Sources

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

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