Skip to main content
VulnerabilityPublished

CVE-2024-23168: XSOverlay · Missing Origin Validation in WebSockets

Affects XSOverlaySource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 647 as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 647
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Aug 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade xiexe/XSOverlay to 647.

Affected software

ProductAffectedFixed in
GitHubxiexe/XSOverlaypkg:github/xiexe/XSOverlayOther threatsAffected
  • <647
Fixed in
  • 647

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately restrict access to the XSOverlay WebSocket API by implementing network-level controls such as firewalls or access control lists to limit connections to trusted sources only.
  2. Employ WebSocket origin validation and enforce strict command validation on the server side to reject unauthorized or malformed messages.
  3. Monitor WebSocket traffic for unusual patterns or unexpected commands indicative of exploitation attempts.
  4. Isolate XSOverlay deployments within segmented network zones to contain potential compromises and prevent lateral movement.
  5. Stay alert for official patches or updates from Xiexe and apply them promptly once available.
  6. If patching is not immediately possible, consider disabling WebSocket functionality or limiting its use to internal, trusted environments.
  7. Conduct security awareness training for teams managing XSOverlay deployments to recognize and respond to suspicious activity.
  8. Implement endpoint detection and response (EDR) solutions to detect arbitrary code execution behaviors related to this vulnerability.

Description

Vulnerability in Xiexe XSOverlay before build 647 allows non-local websites to send the malicious commands to the WebSocket API, resulting in the arbitrary code execution.

References

Community reviews

Loading reviews…