dbcve.org
Charge PortalApplication · Ctek

CVE-2026-27649

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
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.

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

The WebSocket backend for charging station management uses insufficiently random session identifiers that can be predicted, and fails to enforce uniqueness—allowing multiple endpoints to connect with the same session ID. This enables session hijacking where a malicious connection displaces the legitimate station and intercepts backend commands, or denial-of-service through repeated connection requests.

MitigationImplement cryptographically random session identifiers, enforce single active session per charging station with immediate invalidation of previous sessions, and add session validation/renewal on each command.

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
Charge PortalApplication
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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 Ctek Charge Portal WebSocket backend is in use
    Identify if the environment runs Ctek Charge Portal and has WebSocket endpoints enabled for charging station communication. Check for listening ports or services handling OCPP (Open Charge Point Protocol) or similar charging station protocols over WebSocket.
    Affected if The Ctek Charge Portal with WebSocket-based charging station management is deployed and active.
  2. Analyze session ID generation mechanism
    Inspect the session identifier generation code or configuration for the WebSocket connections. Look for the method used to create session IDs, check if they use cryptographically secure random number generators (CSPRNG) or weak/prandom sources.
    Affected if Session IDs are generated using predictable methods (e.g., sequential numbers, timestamp-based IDs, weak PRNG) rather than cryptographically random values.
  3. Test session ID uniqueness enforcement
    Attempt to establish multiple WebSocket connections using the same session identifier from different endpoints. Observe whether the system allows both connections or rejects the duplicate.
    Affected if The system permits multiple concurrent WebSocket connections with identical session identifiers.
  4. Verify session displacement behavior
    Connect a legitimate charging station, then connect another endpoint using the same session ID. Check if the original connection is forcibly disconnected or remains active.
    Affected if Newer connections with duplicate session IDs silently displace legitimate stations without validation or notification.
  5. Review connection logs for session anomalies
    Examine WebSocket connection logs for patterns indicating duplicate session IDs, rapid reconnection attempts from different sources, or unexpected session termination events.
    Affected if Logs show multiple distinct sources connecting with identical session IDs or unexplained session takeovers.

A user is affected if the Ctek Charge Portal WebSocket backend is active AND either session IDs are predictably generated OR duplicate session IDs can be established concurrently.

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 cryptographically random session identifiers, enforce single active session per charging station with immediate invalidation of previous sessions, and add session validation/renewal on each command.

Fix this in Charge Portal Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27649 — 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-27649 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