dbcve.org
Ev2go.ioApplication · Ev2go

CVE-2026-24731

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

WebSocket endpoints for OCPP (Open Charge Point Protocol) charging stations lack proper authentication, allowing unauthenticated attackers to connect using a known or discovered station identifier and impersonate legitimate chargers. This enables attackers to issue or receive OCPP commands, manipulate backend data, and gain unauthorized control over charging infrastructure.

MitigationImplement strong authentication for WebSocket connections (such as mutual TLS, certificate-based authentication, or token-based authentication) and validate station identifiers before allowing connections to prevent impersonation attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ev2go.ioApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Ev2go Ev2go.io deployment
    Identify if your environment includes Ev2go Ev2go.io by reviewing installed software, container images, or service inventory
    Affected if The product Ev2go Ev2go.io is deployed in your environment
  2. Locate OCPP WebSocket endpoints
    Review your network configuration, API gateway settings, or load balancer rules to identify exposed OCPP WebSocket endpoints (typically paths like /ocpp, /ws/ocpp, or similar)
    Affected if OCPP WebSocket endpoints are publicly or internally accessible without proper authentication barriers
  3. Test WebSocket authentication requirement
    Attempt to establish a WebSocket connection to the OCPP endpoint using a tool like wscat or a simple script without providing any authentication credentials
    Affected if Connection is established successfully without requiring any authentication token, certificate, or credentials
  4. Verify station identifier validation
    Inspect the server-side configuration or logs to determine whether station identifiers are validated against an approved whitelist or verified before accepting commands
    Affected if Station identifiers are not validated or any arbitrary identifier can be used to connect
  5. Check for mTLS or token-based authentication
    Review server configuration files, TLS settings, or authentication middleware to determine if mutual TLS or token-based authentication is enforced on WebSocket connections
    Affected if Neither certificate-based mTLS nor token-based authentication is configured for WebSocket endpoints

You are affected if Ev2go Ev2go.io is deployed and OCPP WebSocket endpoints accept connections without requiring authentication or validating station identifiers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strong authentication for WebSocket connections (such as mutual TLS, certificate-based authentication, or token-based authentication) and validate station identifiers before allowing connections to prevent impersonation attacks.

Fix this in Ev2go.io Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing10.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24731 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24731 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data