Skip to main content
CVE-2024-29401VulnerabilityPublished Updated

CVE-2024-29401: xzs-mysql · n/a

Affects xzs-mysqlSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 55% 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:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Mar 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
GitHubmenghaining/xzs-mysqlpkg:github/menghaining/xzs-mysqlOther threatsAffected
  • =3.8
Fixed in–

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

AI-suggested

To mitigate CVE-2024-29401, organizations should immediately audit their session management policies and implement strict session expiration controls, especially for administrative accounts. If patches or updates from the vendor become available, they must be applied without delay. In the absence of official patches, organizations should consider the following practical steps: 1) Manually invalidate all active sessions associated with deleted or disabled admin accounts; 2) Implement short session timeouts and enforce re-authentication for privileged operations; 3) Monitor session activity logs for anomalies such as usage of sessions belonging to deleted users; 4) Restrict network access to the database to trusted hosts and enforce strong network segmentation; 5) Employ multi-factor authentication and least privilege principles to reduce the risk of session hijacking; 6) Conduct regular security assessments and penetration testing focused on session management weaknesses. Additionally, organizations should prepare incident response plans to quickly detect and respond to any exploitation attempts.

Description

xzs-mysql 3.8 is vulnerable to Insufficient Session Expiration, which allows attackers to use the session of a deleted admin to do anything.

References

Community reviews

Loading reviews…