# CVE-2025-5747: WOLFBOX Level 2 EV Charger MCU Command Parsing Misinterpretation of Input Remote Code Execution Vulnerability

> Network-adjacent attackers with authentication can execute arbitrary code on WOLFBOX Level 2 EV Chargers due to improper MCU command frame parsing.

- **Severity:** High 8.0 (`CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jun 2025
- **Updated:** 6 Jun 2025
- **Also known as:** GHSA-x34v-hhv2-p545

## What is CVE-2025-5747?

CVE-2025-5747 is a high-severity code injection vulnerability in WOLFBOX Level 2 EV Charger, published on 6 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

WOLFBOX Level 2 EV Charger MCU Command Parsing Misinterpretation of Input Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installatons of WOLFBOX Level 2 EV Charger devices. Authentication is required to exploit this vulnerability.

The specific flaw exists within the handling of command frames received by the MCU. When parsing frames, the process does not properly detect the start of a frame, which can lead to misinterpretation of input. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the device. Was ZDI-CAN-26501.

Weakness: CWE-115 (Misinterpretation of Input)

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

It affects 1 product.


Products: Wolfbox Level 2 Ev Charger Firmware.

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

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

## Is CVE-2025-5747 being exploited?

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

## Other vulnerabilities in WOLFBOX Level 2 EV Charger

- [CVE-2025-5750](https://insights.sbomify.com/CVE-2025-5750/): Memory corruption in Level 2 EV Charger (high 8.8)
- [CVE-2025-5748](https://insights.sbomify.com/CVE-2025-5748/): WOLFBOX Level 2 EV Charger LAN OTA Exposed Dangerous Method Remote Code Execution Vulnerability (high 8.0)
- [CVE-2025-5749](https://insights.sbomify.com/CVE-2025-5749/): WOLFBOX Level 2 EV Charger BLE Encryption Keys Uninitialized Variable Authentication Bypass Vulnerability (medium 6.3)
- [CVE-2025-5751](https://insights.sbomify.com/CVE-2025-5751/): WOLFBOX Level 2 EV Charger Management Card Hard-coded Credentials Authentication Bypass Vulnerability (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5747 is a high-severity code injection vulnerability in WOLFBOX Level 2 EV Charger, published on 6 Jun 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-5747 in the wild and no public exploit code.

Affected product: WOLFBOX Level 2 EV Charger. 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-5747/ (Markdown: https://insights.sbomify.com/CVE-2025-5747/index.md)
```

## Sources

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

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