CVE-2026-27772
Received Received - Intake
Unauthenticated WebSocket Access Enables OCPP Station Impersonation

Publication date: 2026-02-27

Last updated on: 2026-03-05

Assigner: ICS-CERT

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-27
Last Modified
2026-03-05
Generated
2026-05-27
AI Q&A
2026-02-27
EPSS Evaluated
2026-05-25
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
ev.energy ev.energy *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability involves WebSocket endpoints that lack proper authentication mechanisms. Because of this, attackers can impersonate charging stations without authorization by connecting to the OCPP WebSocket endpoint using a known or discovered charging station identifier.

Once connected, the attacker can issue or receive OCPP commands as if they were a legitimate charger, enabling unauthorized control and manipulation of data sent to the backend.


How can this vulnerability impact me? :

The vulnerability can lead to several serious impacts including privilege escalation and unauthorized control of charging infrastructure.

  • Attackers can impersonate legitimate charging stations.
  • Unauthorized manipulation and corruption of charging network data reported to the backend.
  • Potential disruption or misuse of charging services.

How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability involves unauthenticated access to WebSocket endpoints used by charging stations, where attackers can impersonate stations by connecting with known or discovered identifiers. Detection would involve monitoring network traffic for unauthorized or suspicious WebSocket connections to the OCPP endpoint, especially those that do not follow expected authentication patterns.

Specific commands or tools to detect this vulnerability are not provided in the available resources.


What immediate steps should I take to mitigate this vulnerability?

The vulnerability arises because WebSocket endpoints lack proper authentication, allowing unauthorized access and control. Immediate mitigation steps would logically include implementing authentication mechanisms on the WebSocket endpoints to ensure only legitimate charging stations can connect.

No explicit mitigation steps or recommendations are provided in the available resources.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart