Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-24912: CWE-613 in ePower epower.ie

0
High
VulnerabilityCVE-2026-24912cvecve-2026-24912cwe-613
Published: Thu Mar 05 2026 (03/05/2026, 23:38:11 UTC)
Source: CVE Database V5
Vendor/Project: ePower
Product: epower.ie

Description

The WebSocket backend uses charging station identifiers to uniquely associate sessions but allows multiple endpoints to connect using the same session identifier. This implementation results in predictable session identifiers and enables session hijacking or shadowing, where the most recent connection displaces the legitimate charging station and receives backend commands intended for that station. This vulnerability may allow unauthorized users to authenticate as other users or enable a malicious actor to cause a denial-of-service condition by overwhelming the backend with valid session requests.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/13/2026, 19:41:02 UTC

Technical Analysis

CVE-2026-24912 is a vulnerability classified under CWE-613 (Insufficient Session Expiration) affecting the ePower epower.ie product. The issue arises from the WebSocket backend's use of charging station identifiers as session identifiers, which are predictable and allow multiple endpoints to connect simultaneously using the same session ID. This design flaw permits session hijacking or session shadowing attacks, where an attacker’s connection can displace the legitimate charging station’s session and receive backend commands intended for that station. The vulnerability also enables a denial-of-service (DoS) condition by allowing an attacker to flood the backend with numerous valid session requests, overwhelming system resources. The vulnerability is remotely exploitable over the network without requiring authentication or user interaction, increasing its risk. The CVSS v3.1 base score is 7.3, reflecting high severity with network attack vector, low attack complexity, no privileges required, and impacts on confidentiality, integrity, and availability. The vulnerability affects all versions of epower.ie, and no patches or known exploits are currently reported. The root cause is insufficient session management and predictable session identifiers in the WebSocket implementation, violating secure session handling best practices.

Potential Impact

This vulnerability can have significant impacts on organizations operating ePower epower.ie charging station management systems. Unauthorized session hijacking could allow attackers to impersonate legitimate charging stations, potentially manipulating charging commands, disrupting operations, or gaining unauthorized access to system functions. This compromises confidentiality and integrity of communications between backend and charging stations. Additionally, the ability to cause denial-of-service by flooding the backend with session requests can disrupt service availability, impacting business continuity and customer trust. Given the critical role of charging infrastructure in energy and transportation sectors, exploitation could lead to operational disruptions, financial losses, and reputational damage. The lack of authentication and user interaction requirements increases the likelihood of exploitation, especially in environments exposed to the internet or untrusted networks.

Mitigation Recommendations

To mitigate this vulnerability, organizations should implement the following specific measures: 1) Update the WebSocket backend to use cryptographically secure, unpredictable session identifiers that are unique per connection and expire appropriately to prevent reuse or session shadowing. 2) Enforce strict session management policies that disallow multiple simultaneous connections using the same session identifier. 3) Implement backend rate limiting and connection throttling to mitigate denial-of-service attempts by limiting the number of concurrent sessions from a single source or overall. 4) Employ mutual authentication mechanisms between charging stations and backend to ensure only authorized devices can establish sessions. 5) Monitor WebSocket connections for anomalous behavior such as rapid reconnections or multiple connections from the same session ID. 6) If available, apply vendor patches or updates addressing this vulnerability as soon as they are released. 7) Segment the network to restrict access to the WebSocket backend only to trusted devices and networks. 8) Conduct regular security assessments and penetration testing focused on session management and WebSocket implementations.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
icscert
Date Reserved
2026-02-24T00:23:47.066Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69aa1962c48b3f10ff8d2b04

Added to database: 3/6/2026, 12:01:38 AM

Last enriched: 3/13/2026, 7:41:02 PM

Last updated: 4/19/2026, 8:39:51 PM

Views: 42

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses