# CVE-2025-3881: eCharge Hardy Barth cPH2 check_req.php ntp Command Injection Remote Code Execution Vulnerability

> Network-adjacent attackers can execute arbitrary code on eCharge Hardy Barth cPH2 charging stations via command injection in the ntp parameter.

- **Severity:** High 8.8 (`CVSS:3.0/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 May 2025
- **Updated:** 22 May 2025
- **Also known as:** GHSA-56c3-5jh4-v4v3

## What is CVE-2025-3881?

CVE-2025-3881 is a high-severity command injection vulnerability in eCharge Hardy Barth cPH2, published on 22 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

eCharge Hardy Barth cPH2 check_req.php ntp Command Injection Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of eCharge Hardy Barth cPH2 charging stations. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the handling of the ntp parameter provided to the check_req.php endpoint. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of the www-data user. Was ZDI-CAN-23113.

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

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

It affects 1 product.


Products: Hardy-Barth Cph2 Echarge Firmware.

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

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

## Is CVE-2025-3881 being exploited?

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

## Other vulnerabilities in eCharge Hardy Barth cPH2

- [CVE-2023-46359](https://insights.sbomify.com/CVE-2023-46359/): Command injection in n/a (critical 9.8)
- [CVE-2025-3882](https://insights.sbomify.com/CVE-2025-3882/): eCharge Hardy Barth cPH2 nwcheckexec.php dest Command Injection Remote Code Execution Vulnerability (high 8.8)
- [CVE-2025-3883](https://insights.sbomify.com/CVE-2025-3883/): eCharge Hardy Barth cPH2 index.php Command Injection Remote Code Execution Vulnerability (high 8.8)
- [CVE-2023-46360](https://insights.sbomify.com/CVE-2023-46360/): Privilege escalation in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3881 is a high-severity command injection vulnerability in eCharge Hardy Barth cPH2, published on 22 May 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-3881 in the wild and no public exploit code.

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

## Sources

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

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