# CVE-2025-27804: OS Command Injection Vulnerability in eCharge Hardy Barth cPH2 / cPP2 charging stations

> Attackers can execute arbitrary OS commands with root privileges on eCharge Hardy Barth charging stations via crafted MQTT messages.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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:** 21 May 2025
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-xw2w-jc5r-g6r7

## What is CVE-2025-27804?

CVE-2025-27804 is a medium-severity command injection vulnerability in eCharge Hardy Barth cPH2 / cPP2 charging stations, published on 21 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Several OS command injection vulnerabilities exist in the device firmware in the /var/salia/mqtt.php script. By publishing a specially crafted message to a certain MQTT topic arbitrary OS commands can be executed with root permissions.

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

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


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

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

## Is CVE-2025-27804 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27804 is a medium-severity command injection vulnerability in eCharge Hardy Barth cPH2 / cPP2 charging stations, published on 21 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-27804 in the wild and no public exploit code.

Affected product: eCharge Hardy Barth cPH2 / cPP2 charging stations. 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-27804/ (Markdown: https://insights.sbomify.com/CVE-2025-27804/index.md)
```

## Sources

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

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