dbcve.org
Cph2 Echarge FirmwareOperating system · Hardy Barth

CVE-2025-3881

HIGH · 8.8 CVSS v3.0 Published 2025-05-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A command injection vulnerability exists in the check_req.php endpoint of eCharge Hardy Barth cPH2 charging stations. The 'ntp' parameter is not validated before being used in a system call, allowing attackers to inject arbitrary shell commands. No authentication is required, and the exploit runs in the context of the www-data user.

MitigationApply vendor firmware updates when available. Until then, network-segment the charging stations to limit exposure to untrusted network segments and implement WAF rules to detect and block command injection attempts in the ntp parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cph2 Echarge FirmwareOperating system
Affected:= 2.0.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the charging station's web interface or check the device label/metadata to confirm it is a Hardy Barth cPH2 charging station. Look for manufacturer branding and model designation.
    Affected if The device is NOT a Hardy Barth cPH2 model - you are not affected by this specific CVE.
  2. Check the firmware version
    Navigate to the charging station's admin or status page in the web interface, or use SNMP/SSH if available, to retrieve the installed firmware version.
    Affected if The firmware version is 2.0.4 - you are running the affected version.
  3. Verify the check_req.php endpoint exists
    Attempt to access http://[device-ip]/check_req.php via HTTP GET request. The endpoint may be located in /cgi-bin/ or the web root depending on installation.
    Affected if The endpoint returns a valid HTTP response (200 or other) indicating it is present and accessible.
  4. Confirm NTP parameter is accepted
    Send a GET request to the check_req.php endpoint with a test parameter such as ?ntp=test to see if the parameter is processed without error.
    Affected if The endpoint accepts and processes the ntp parameter without rejecting or sanitizing the input.
  5. Check network exposure
    Review firewall rules, VLAN configuration, or network ACLs to determine if the charging station's web interface is accessible from untrusted networks or the internet.
    Affected if The device web interface is directly accessible from untrusted networks without authentication barriers.

You are affected if you have a Hardy Barth cPH2 charging station running firmware 2.0.4 with the check_req.php endpoint accessible and the NTP parameter feature enabled, particularly if the interface is exposed to untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware updates when available. Until then, network-segment the charging stations to limit exposure to untrusted network segments and implement WAF rules to detect and block command injection attempts in the ntp parameter.

Fix this in Cph2 Echarge Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,312.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3881 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-3881 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data