<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Cloudcharge.se - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/cloudcharge.se/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Sat, 13 Jun 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/cloudcharge.se/feed.xml" rel="self" type="application/rss+xml"/><item><title>CloudCharge Vulnerabilities Allow Charging Station Impersonation and DoS</title><link>https://feed.craftedsignal.io/briefs/2026-06-cloudcharge-vulns/</link><pubDate>Sat, 13 Jun 2026 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-06-cloudcharge-vulns/</guid><description>Multiple vulnerabilities in CloudCharge cloudcharge.se allow attackers to impersonate charging stations, hijack sessions, cause denial of service, and manipulate backend data, impacting energy and transportation sectors.</description><content:encoded><![CDATA[<p>Multiple vulnerabilities have been identified in CloudCharge cloudcharge.se, a charging station management platform. These vulnerabilities, including CVE-2026-20781, CVE-2026-25114, CVE-2026-27652, and CVE-2026-20733, could allow attackers to compromise charging stations and backend systems. Specifically, the lack of proper authentication and session management in the WebSocket API enables unauthorized access and control. Given that the vulnerable software is used within the Energy and Transportation Systems sectors worldwide, successful exploitation could disrupt critical infrastructure. The vendor has not responded to coordination requests.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker identifies a publicly accessible charging station identifier via web-based mapping platforms (CVE-2026-20733).</li>
<li>The attacker connects to the OCPP WebSocket endpoint of a CloudCharge charging station using the discovered identifier (CVE-2026-20781).</li>
<li>Due to the missing authentication mechanisms, the attacker successfully impersonates a legitimate charger (CVE-2026-20781).</li>
<li>The attacker exploits the lack of rate limiting and floods the authentication endpoint with requests, causing a denial-of-service condition by suppressing legitimate charger telemetry (CVE-2026-25114).</li>
<li>Alternatively, the attacker exploits the predictable session identifiers and attempts to hijack an existing charging session (CVE-2026-27652).</li>
<li>The attacker sends malicious OCPP commands to manipulate charging processes or corrupt charging network data reported to the backend (CVE-2026-20781).</li>
<li>The attacker displaces the legitimate charging station's connection, receiving backend commands intended for the original station (CVE-2026-27652).</li>
<li>The ultimate objective is to disrupt charging services, manipulate billing information, or gain persistent access to the charging infrastructure backend.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of these vulnerabilities could have significant consequences, particularly in the Energy and Transportation Systems sectors. Attackers could disrupt electric vehicle charging services, leading to widespread outages and transportation delays. Compromised charging stations could be used to manipulate billing information, causing financial losses for both customers and charging station operators. A large-scale denial-of-service attack could overwhelm the CloudCharge backend, rendering entire charging networks inoperable. Given the worldwide deployment of CloudCharge, the impact could be felt across multiple countries.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Monitor network connections to the CloudCharge infrastructure for suspicious WebSocket traffic originating from unexpected sources, using the <code>Detect Suspicious CloudCharge WebSocket Connection</code> Sigma rule.</li>
<li>Implement rate limiting on authentication requests to the CloudCharge WebSocket API to mitigate denial-of-service attempts, referencing the information about CVE-2026-25114.</li>
<li>Monitor logs for multiple connections using the same charging station identifier, indicating potential session hijacking attempts, using the <code>Detect CloudCharge Session Hijacking</code> Sigma rule and the context for CVE-2026-27652.</li>
<li>Review and restrict access to web-based mapping platforms that may expose charging station authentication identifiers, mitigating the risk associated with CVE-2026-20733.</li>
<li>Contact CloudCharge directly via their support page (<a href="https://cloudcharge.tech/support/contact/">https://cloudcharge.tech/support/contact/</a>) to inquire about available patches or mitigations for CVE-2026-20781, CVE-2026-25114, CVE-2026-27652, and CVE-2026-20733.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>cloudcharge</category><category>ics</category><category>vulnerability</category><category>dos</category></item></channel></rss>