# CVE-2025-9494: Viessmann Vitogate 300 OS Command Injection

> An authenticated attacker can inject arbitrary OS commands via the Vitogate 300 web interface to gain code execution on the device.

- **Severity:** High 8.5 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2025
- **Updated:** 23 Sep 2025
- **Also known as:** GHSA-75cp-gjjh-3r55

## What is CVE-2025-9494?

CVE-2025-9494 is a high-severity command injection vulnerability in Viessmann Vitogate 300, published on 23 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An OS command injection vulnerability has been discovered in the Vitogate 300, which can be exploited by malicious users to compromise affected installations. Specifically, the `/cgi-bin/vitogate.cgi` endpoint is affected, when the `form` JSON parameter is set to `form-0-2`. The vulnerability stems from the fact that that function at offset 0x21c24 does not properly sanitize supplied input before interpolating it into a format string which gets passed to `popen()`. Consequently, an authenticated attacker is able to inject arbitrary OS commands and thus gain code execution on affected devices.

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

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


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

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

## Is CVE-2025-9494 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9494 is a high-severity command injection vulnerability in Viessmann Vitogate 300, published on 23 Sep 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-9494 in the wild and no public exploit code.

Affected product: Viessmann Vitogate 300. 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-9494/ (Markdown: https://insights.sbomify.com/CVE-2025-9494/index.md)
```

## Sources

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

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