The absence of authentication on OCPP WebSocket endpoints allows unauthenticated attackers to hijack charging station identities and manipulate backend infrastructure.

This vulnerability stems from the lack of authentication mechanisms on WebSocket endpoints. Attackers can connect using a known charger ID and interact with the backend as a legitimate station without providing credentials.

Attackers can gain unauthorized control over charging infrastructure and corrupt the data reported to the backend. This can lead to financial loss, privilege escalation, and significant reputational damage. The CVSS score of 9.4 underscores the critical risk to charging network operators.

Immediate Action: Apply security updates to the OCPP backend to require authentication for all incoming WebSocket connections.

Proactive Monitoring: Audit backend logs for station IDs that connect from multiple locations or show unusual data patterns.

Compensating Controls: Deploy a secure proxy or gateway that requires authentication before forwarding traffic to the OCPP WebSocket endpoint.

Public Exploit Available: No

Immediate action is required to secure the OCPP communication channel. Enforcing strong, per-device authentication is the only way to mitigate the risk of station impersonation and data corruption.