Security readout for executives and security teams
Plain-English summary
SteVe, an EV charging management system, can let one authenticated charger stop another charger’s active charging session. The weakness affects versions up to and including 3.11.0. Business impact is mainly service disruption: charging sessions may be terminated across a managed network. Public sources do not show confirmed active exploitation.
Executive priority
Treat as a near-term remediation item for EV charging operators using SteVe. The issue can disrupt charging availability, but current public evidence does not support emergency prioritization absent exposure to untrusted chargers or related SOAP endpoint weaknesses.
Technical view
StopTransaction handling looks up transactions only by transactionId, a sequential integer, without confirming the requesting chargeBoxId owns the transaction. Validation confirms the transaction exists and is not already stopped, but not charger identity. The advisory identifies OcppServerRepositoryImpl.getTransaction() as the root cause and points to commit 7f169c6c5b36a9c458ec41ce8af581972e5c724e as the fix.
Likely exposure
Organizations running steve-community SteVe versions <= 3.11.0 are potentially exposed, especially where untrusted or third-party chargers can authenticate to the management system. Exposure may be higher if related unauthenticated SOAP endpoint issues are present, as described in the advisory text.
Exploitation context
The CVSS vector indicates network access, low complexity, low privileges, no user interaction, and high availability impact. The sources describe proof-of-concept feasibility, but Glexia has no cited evidence of active exploitation or CISA KEV listing for this CVE.
Researcher notes
The key security boundary is transaction ownership between charger identities. Validate the fix by confirming StopTransaction cannot affect transactions belonging to another chargeBoxId. Avoid assuming unauthenticated exposure unless the related SOAP endpoint finding also applies in the assessed environment.
Mitigation direction
- Identify all SteVe deployments and their versions.
- Prioritize systems running SteVe <= 3.11.0.
- Apply the vendor fix commit or a release containing it when available.
- If no packaged release exists, evaluate backporting the ownership check.
- Review vendor guidance before making production changes.
- Restrict charger onboarding to trusted devices where operationally possible.
Validation and detection
- Confirm whether SteVe version is <= 3.11.0.
- Review StopTransaction handling for chargeBoxId ownership verification.
- Verify transaction lookup includes the requesting charger identity.
- Check whether the fix commit is present in deployed code.
- Review logs for unusual StopTransaction activity across chargers.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-28230 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.7 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
5.7MediumVector: 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 materials
- CVE List V5 sourceCVE List V5
- https://github.com/steve-community/steve/security/advisories/GHSA-6x38-4w7h-cwr8CVE reference · x_refsource_CONFIRM
- https://github.com/steve-community/steve/commit/7f169c6c5b36a9c458ec41ce8af581972e5c724eCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.