{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68930 exists.","fix":"No fix has been published for CVE-2025-68930 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-68930 is a high-severity vulnerability in traccar, published on 23 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-68930 and fix it if it is affected.\n\nWhat it is: CVE-2025-68930 is a high-severity vulnerability in traccar, published on 23 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68930 exists.\n\nAffected product: traccar. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-68930/ (Markdown: https://insights.sbomify.com/CVE-2025-68930/index.md)","id":"CVE-2025-68930","markdown":"https://insights.sbomify.com/CVE-2025-68930/index.md","name":"CVE-2025-68930","record":{"aliases":["GHSA-69x6-wcx2-vghp"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"GPS tracking system","requires_auth":"none","summary":"Attackers can hijack WebSocket connections to access user data due to missing Origin header validation in Traccar.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"traccar","vendor":"traccar"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-1385","name":"Missing Origin Validation in WebSockets"}],"description":"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 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.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2026-05-04","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-05-04","kind":"exploitdb","ref":"52545","stars":null,"title":"Traccar GPS Tracking System 6.11.1 - Cross-Site WebSocket Hijacking (CSWSH)"},{"date":"2026-05-04T16:29:30Z","kind":"github_poc","ref":"https://github.com/kaleth4/CVE-2025-68930","stars":0,"title":null}],"tier":"weaponised"},"has_fix":false,"headline":"Traccar Missing Origin Validation in WebSockets","id":"CVE-2025-68930","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Jervis has AES CBC Mode Without Authentication","id":"CVE-2025-68931"},"packages":[],"prev":{"headline":"Frappe may be vulnerable remote code execution due to server-side template injection","id":"CVE-2025-68929"},"products":["traccar"],"published":"2026-02-23","related":[{"cvss_score":9.7,"headline":"Traccar's unrestricted file upload vulnerability in device image upload could lead to remote code execution","id":"CVE-2024-31214","kev_date_added":null,"published":"2024-04-10"},{"cvss_score":9.5,"headline":"Use of default credentials at Traccar fleet management solution","id":"CVE-2024-7746","kev_date_added":null,"published":"2024-08-13"},{"cvss_score":8.7,"headline":"Traccar Vulnerable to Stored Cross-Site Scripting (XSS) via Malicious SVG File Upload","id":"CVE-2026-25648","kev_date_added":null,"published":"2026-02-23"},{"cvss_score":8.5,"headline":"An unrestricted file upload vulnerability in traccar leads to RCE","id":"CVE-2023-50729","kev_date_added":null,"published":"2024-01-15"},{"cvss_score":7.7,"headline":"LDAP injection vulnerability in Traccar GPS Tracking System","id":"CVE-2020-5246","kev_date_added":null,"published":"2020-07-14"},{"cvss_score":7.3,"headline":"Traccar Vulnerable to Authorization Code Theft via Open Redirect in OIDC Provider Endpoints","id":"CVE-2026-25649","kev_date_added":null,"published":"2026-02-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-25","vendors":["traccar"]},"summary":"Attackers can hijack WebSocket connections to access user data due to missing Origin header validation in Traccar.","url":"https://insights.sbomify.com/CVE-2025-68930/"}