Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2026-28230— In SteVe, any authenticated charger can terminate any other charger's active transaction (missing ownership verification on StopTransaction)

Quick assessment

Affected
steve-community steve
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

SteVe是SteVe Community开源的一个开放平台。用于实施、测试和评估电动汽车的新颖想法,例如身份验证协议、充电点预留机制以及电动汽车的商业模式。 SteVe 3.11.0及之前版本存在访问控制错误漏洞,该漏洞源于处理StopTransaction消息时未验证请求充电器与原始启动交易的充电器是否匹配,可能导致任意充电器会话被终止。

AI Predicted 9.1 Difficulty: Easy EPSS 0.28% · P19

Possible ATT&CK Techniques 1 AI

T1190 · Exploit Public-Facing Application
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-28230

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
In SteVe, any authenticated charger can terminate any other charger's active transaction (missing ownership verification on StopTransaction)
Source: CVE Program / CVE List V5
Vulnerability Description
SteVe is an open-source EV charging station management system. In versions up to and including 3.11.0, when a charger sends a StopTransaction message, SteVe looks up the transaction solely by transactionId (a sequential integer starting from 1) without verifying that the requesting charger matches the charger that originally started the transaction. Any authenticated charger can terminate any other charger’s active session across the entire network. The root cause is in OcppServerRepositoryImpl.getTransaction() which queries only by transactionId with no chargeBoxId ownership check. The validator checks that the transaction exists and is not already stopped but never verifies identity. As an attacker controlling a single registered charger I could enumerate sequential transaction IDs and send StopTransaction messages targeting active sessions on every other charger on the network simultaneously. Combined with FINDING-014 (unauthenticated SOAP endpoints), no registered charger is even required — the attack is executable with a single curl command requiring only a known chargeBoxId. Commit 7f169c6c5b36a9c458ec41ce8af581972e5c724e contains a fix for the issue.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P
Source: CVE Program / CVE List V5
Vulnerability Type
访问控制不恰当
Source: CVE Program / CVE List V5
Vulnerability Title
SteVe 访问控制错误漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
SteVe是SteVe Community开源的一个开放平台。用于实施、测试和评估电动汽车的新颖想法,例如身份验证协议、充电点预留机制以及电动汽车的商业模式。 SteVe 3.11.0及之前版本存在访问控制错误漏洞,该漏洞源于处理StopTransaction消息时未验证请求充电器与原始启动交易的充电器是否匹配,可能导致任意充电器会话被终止。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
steve-community steve <= 3.11.0 -

II. Public POCs for CVE-2026-28230

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-28230

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-28230 (1)

Vendor Advisories for CVE-2026-28230 (1)

IV. Related Vulnerabilities

V. Comments for CVE-2026-28230

No comments yet


Leave a comment