Ev2go.Io
CVE-2026-24731
CRITICAL
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
Lifecycle Timeline
2DescriptionCVE.org
WebSocket endpoints lack proper authentication mechanisms, enabling attackers to perform unauthorized station impersonation and manipulate data sent to the backend. An unauthenticated attacker can connect to the OCPP WebSocket endpoint using a known or discovered charging station identifier, then issue or receive OCPP commands as a legitimate charger. Given that no authentication is required, this can lead to privilege escalation, unauthorized control of charging infrastructure, and corruption of charging network data reported to the backend.
AnalysisAI
Missing WebSocket authentication vulnerability identical to CVE-2026-20781. Unauthenticated attackers can perform station impersonation and data injection via unprotected WebSocket endpoints.
Technical ContextAI
CWE-306 on a different WebSocket endpoint in the same industrial platform. Same root cause: missing authentication mechanism.
RemediationAI
Apply vendor patch addressing all WebSocket authentication issues. Restrict network access to management interfaces.
Ev2go.Io's WebSocket API lacks authentication rate limiting, enabling attackers to launch denial-of-service attacks that
Session hijacking in Ev2go.Io's WebSocket backend allows remote attackers to impersonate legitimate charging stations an
Ev2go.Io charging stations expose authentication credentials through publicly accessible web-based mapping platforms, al
Same technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today