Skip to content
Web

CVE-2025-54322

10.0
Critical
EPSS 15%Dec 27, 2025

Root remote code execution via base64 Python in chkid param (vLogin.py).

common questions

Is CVE-2025-54322 being exploited?

Not confirmed. CVE-2025-54322 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 15% probability of exploitation in the next 30 days.

How severe is CVE-2025-54322?

CVE-2025-54322 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-54322?

Not known from our data. No patch reference has been recorded for CVE-2025-54322, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2025-54322 affect?

CVE-2025-54322 affects Xspeeder SXZOS, vLogin.py, chkid parameter. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-54322?

Apply patch when available; implement input validation for chkid; monitor for exploitation.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Xspeeder SXZOSvLogin.pychkid parameter
impact

Remote code execution and full control on affected server via crafted base64 Python payload in chkid parameter.

action required

Immediate action required

affected versions
Xspeeder SXZOS
  • affected<= 2025-12-26

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free