Arbitrary file overwrite via unchecked upload filename
Published Jul 13, 2026 · Updated Jul 13, 2026
Arbitrary file overwrite in EVbee DC-80 before 1.5.1 allows remote attackers to write files through a certificate-update endpoint. The endpoint handler uses the unverified Content-Disposition filename as a filesystem destination, allowing attacker-controlled paths. No authentication is required; overwriting system files can interrupt service, while code execution requires a separately triggered overwritten shell script.
Summary
What happened
Arbitrary file overwrite in EVbee DC-80 before 1.5.1 allows remote attackers to write files through a certificate-update endpoint. The endpoint handler uses the unverified Content-Disposition filename as a filesystem destination, allowing attacker-controlled paths. No authentication is required; overwriting system files can interrupt service, while code execution requires a separately triggered overwritten shell script.
The record
- CVE
- CVE-2026-22102
- Published
- Jul 13, 2026
- Updated
- Jul 13, 2026
- Vendor
- EVbee
- Product
- DC 60&80
- Classifications
- CWE-20, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 13, 2026CVE publishedPublication date reported by the CVE source.
- Jul 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.5.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo