Skip to main content
VulnerabilityPublished Updated

CVE-2025-54322: Xspeeder SXZOS · Eval Injection

Affects Xspeeder SXZOSSource CVE Database V5

0

Not known to be exploited · 15% EPSS · CVSS 10.0 Critical.

Data as of 26 Oct 2026, 14:05 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Dec 2025

  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

Affected software

ProductAffectedFixed in
Xspeeder SXZOSAffected
  • =0
Fixed in–

AI-suggested

  1. Immediately restrict network access to the vLogin.py service by implementing firewall rules or network segmentation to limit exposure to trusted hosts only.
  2. Deploy intrusion detection/prevention systems (IDS/IPS) with signatures or heuristics to detect suspicious base64-encoded payloads or anomalous requests targeting the chkid, title, and oIP parameters.
  3. Conduct thorough code audits and input validation reviews on any custom or integrated components interacting with vLogin.py to identify and remediate unsafe eval usage.
  4. Monitor system logs and network traffic for unusual activity indicative of exploitation attempts, such as unexpected base64 strings or Python code execution traces.
  5. Engage with Xspeeder vendor support channels to obtain patches or official mitigation guidance as soon as they become available.
  6. Prepare incident response plans specific to remote code execution scenarios to enable rapid containment and recovery.
  7. Consider deploying application-layer firewalls or web application firewalls (WAFs) capable of blocking malicious payloads targeting this vulnerability.
  8. Educate system administrators and security teams about the vulnerability specifics to enhance detection and response capabilities.

Description

Xspeeder SXZOS through 2025-12-26 allows root remote code execution via base64-encoded Python code in the chkid parameter to vLogin.py. The title and oIP parameters are also used.

References

Community reviews

Loading reviews…