# CVE-2026-22103: EVbee DC-80 command injection in NPC start endpoint

Source: https://junglewise.ai/threats/cve-2026-22103-evbee-dc-80-command-injection-in-npc-start-endpoint  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-13. Updated: 2026-07-13  
License: CC BY 4.0 with a link back

CVE-2026-22103 · Severity: info · CVSS 9.3 · Published 2026-07-13

A critical security vulnerability has been identified in EVbee DC-80 electric vehicle charging stations. An attacker can remotely take control of the device by sending malicious commands to its internal web server. This could allow unauthorized parties to disrupt charging services, manipulate device settings, or gain a foothold in the local network.

Technologies: [EVbee DC-80](https://junglewise.ai/threats/technologies/dc-80). Vendors: [EVbee](https://junglewise.ai/threats/vendors/evbee).

## Quick answers

**Is CVE-2026-22103 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-22103 being exploited in the wild.

**How severe is CVE-2026-22103?** Informational severity, with a CVSS score of 9.3, published 13 July 2026.

**Which products and versions are affected?** EVbee DC-80 versions before 1.5.1.

**Is there a fix for CVE-2026-22103?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-22103 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-22103?** Check whether you run EVbee DC-80 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A command injection vulnerability exists in the EVbee DC-80 charging station's web server, specifically within the 'NPC start' endpoint listening on port 8090. The flaw is caused by improper neutralization of special elements used in a command (CWE-77). An unauthenticated remote attacker can exploit this by sending specially crafted requests to the affected endpoint, leading to arbitrary command execution with high privileges. The vulnerability affects versions prior to 1.5.1 and has been assigned a CVSS 4.0 base score of 9.3.

## Affected products

- EVbee DC-80 versions before 1.5.1

## Timeline

- 2026-07-13: advisory: NVD published the CVE record based on DIVD disclosure.
- 2026-07-13: disclosed: Vulnerability disclosed by the Dutch Institute for Vulnerability Disclosure (DIVD).

## References

- [https://csirt.divd.nl/DIVD-2026-00001/](https://csirt.divd.nl/DIVD-2026-00001/)

## Related threats

- [EVbee DC-80 weak hardcoded root password in SSH](https://junglewise.ai/threats/cve-2026-22094-the-firmware-for-the-evbee-dc-80-has-a-weak-hardcoded-root)
- [EVbee DC-80 arbitrary file write via webserver endpoint](https://junglewise.ai/threats/cve-2026-22102-evbee-dc-80-arbitrary-file-write-via-webserver-endpoint)
- [EVbee DC-80 command injection in OCPP ReserveLogin](https://junglewise.ai/threats/cve-2026-22100-evbee-dc-80-command-injection-in-ocpp-reservelogin)
- [EVbee DC-80 improper authentication in Bluetooth interface](https://junglewise.ai/threats/cve-2026-22099-evbee-dc-80-improper-authentication-in-bluetooth-interface)
- [EVbee DC-80 missing signature validation in firmware update](https://junglewise.ai/threats/cve-2026-22097-evbee-dc-80-missing-signature-validation-in-firmware-update)