dbcve.org
Cph2 Echarge FirmwareOperating system · Hardy Barth

CVE-2025-3882

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 nwcheckexec.php dest 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 dest parameter provided to the nwcheckexec.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-23114.

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 nwcheckexec.php endpoint of eCharge Hardy Barth cPH2 charging stations. The dest parameter accepts user-supplied input without validation and passes it directly to a system call, allowing remote attackers to execute arbitrary code as the www-data user. No authentication is required, making this exploitable by any network-adjacent attacker.

MitigationApply vendor-supplied firmware patch when available; until then, network-segment charging stations from untrusted networks and deploy a WAF to filter malicious command injection payloads in the dest 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
    Locate the charging station and confirm it is a Hardy Barth cPH2 model. Check the physical device label or administrative interface for the model number.
    Affected if The device is not a Hardy Barth cPH2 unit, then it is not affected by this specific CVE.
  2. Check the firmware version
    Access the charging station administrative interface or check via the vendor's diagnostic method to determine the installed firmware version.
    Affected if The firmware version is exactly 2.0.4, then this version is confirmed affected. If the version differs (higher or lower), it may not be affected - compare against the affected range.
  3. Verify the nwcheckexec.php endpoint exists
    Attempt to access the URI path /nwcheckexec.php on the charging station web interface. This is the vulnerable endpoint mentioned in the advisory.
    Affected if The endpoint returns a valid response (rather than 404), the vulnerable script is present and may be exploitable.
  4. Confirm the dest parameter is accepted
    Send an HTTP GET or POST request to nwcheckexec.php with a test value in the dest parameter (e.g., ?dest=test). Observe if the parameter is processed without validation.
    Affected if The parameter is processed and reflected in the response without sanitization, the command injection vulnerability is present.

If the device is a Hardy Barth cPH2 charging station running firmware version 2.0.4 and the nwcheckexec.php endpoint is accessible with an unvalidated dest parameter, the environment is affected by CVE-2025-3882.

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-supplied firmware patch when available; until then, network-segment charging stations from untrusted networks and deploy a WAF to filter malicious command injection payloads in the dest parameter.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3882 — 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-3882 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