# CVE-2026-22102: EVbee DC-80 arbitrary file write via webserver endpoint

Source: https://junglewise.ai/threats/cve-2026-22102-evbee-dc-80-arbitrary-file-write-via-webserver-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-22102 · Severity: info · CVSS 9.3 · Published 2026-07-13

A vulnerability in EVbee DC-80 electric vehicle charging stations allows an attacker to remotely write files to the device's internal storage. By sending a specially crafted web request, an attacker could crash the system by overwriting critical files or gain full control over the device by replacing system scripts. This could lead to service outages or unauthorized access to the charging infrastructure.

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

## Quick answers

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

**How severe is CVE-2026-22102?** 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-22102?** 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-22102 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-22102?** 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

The EVbee DC-80 webserver contains an endpoint that processes POST requests and accepts a filename parameter within the Content-Disposition header without proper validation or sanitization. This improper input validation (CWE-20) allows a remote, unauthenticated attacker to perform arbitrary file writes across the filesystem. By overwriting critical system files, an attacker can cause a denial of service. Alternatively, by overwriting executable shell scripts that are subsequently triggered by other system processes, an attacker can achieve remote code execution (RCE). The vulnerability is addressed in version 1.5.1.

## Affected products

- EVbee DC-80 versions before 1.5.1

## Timeline

- 2026-07-13: disclosed
- 2026-07-13: advisory

## 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 command injection in NPC start endpoint](https://junglewise.ai/threats/cve-2026-22103-evbee-dc-80-command-injection-in-npc-start-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)