CVE-2025-68930
Traccar ≤ 6.11.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:NSummary
CVE-2025-68930 is a high-severity Missing Origin Validation in WebSockets (CWE-1385) vulnerability in Traccar Traccar. Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked at the 43th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-68930 is a Cross-Site WebSocket Hijacking (CSWSH) vulnerability, classified under CWE-1385, affecting versions of the Traccar open-source GPS tracking system up to and including 6.11.1. The issue resides in the `/api/socket` endpoint, where the application does not validate the `Origin` header during the WebSocket handshake. This flaw enables attackers to circumvent the Same Origin Policy (SOP), allowing unauthorized establishment of a full-duplex WebSocket connection.
A remote attacker can exploit this vulnerability without privileges (PR:N) over the network (AV:N) with low complexity (AC:L), though it requires user interaction (UI:R). By tricking a legitimate user into visiting a malicious webpage—such as through a phishing link—the attacker can leverage the user's existing session credentials (JSESSIONID) to hijack the WebSocket connection. Successful exploitation grants high confidentiality impact (C:H) and low integrity impact (I:L), with no availability impact (A:N) and unchanged scope (S:U), as scored at CVSS 7.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N). This could enable real-time data exfiltration or injection of commands on behalf of the victim user.
The GitHub Security Advisory (GHSA-69x6-wcx2-vghp) at the project's repository details the vulnerability but notes that, as of publication on 2026-02-23, it is unclear whether a fix is available. Security practitioners should monitor the Traccar repository for patches and consider implementing custom Origin header validation or WebSocket origin checks as interim mitigations.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-207618
Vulnerability Data
Versions of the Traccar open-source GPS tracking system up to and including 6.11.1 contain a Cross-Site WebSocket Hijacking (CSWSH) vulnerability in the `/api/socket` endpoint. The application fails to validate the `Origin` header during the WebSocket handshake. This allows a remote…
more
attacker to bypass the Same Origin Policy (SOP) and establish a full-duplex WebSocket connection using a legitimate user's credentials (JSESSIONID). As of time of publication, it is unclear whether a fix is available.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V4.4.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces approved authorizations on logical access, which can include origin checks before accepting WebSocket connections.
Enforces information flow policies that can require validation of communication origins at system boundaries.
Protects authenticity of communications sessions, which origin validation helps ensure for WebSocket handshakes.
Monitors and controls communications at external interfaces, directly supporting origin validation for inbound WebSocket traffic.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require origin validation for WebSocket endpoints.
Origin validation is a required step when authenticating WebSocket connection requests.
Enforcing authorization policy on incoming connections can require origin checks.
Network-level controls that block unauthorized logical access can mitigate missing origin checks.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect missing origin validation in WebSocket implementations.
Network security controls can enforce origin validation and restrict WebSocket connections to trusted sources.
Secure configuration of network services can include origin checks for WebSocket endpoints.
Application security requirements can mandate origin validation for WebSocket communications.
Secure architecture principles can require proper origin validation mechanisms in WebSocket implementations.
Secure coding standards can explicitly require origin validation for WebSocket connections.