Skip to main content
VulnerabilityPublished Updated

CVE-2024-33124: cxcxcxcxcxcxcxc · SQL Injection

Affects cxcxcxcxcxcxcxcSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

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.5% chance of exploitation in 30 days – higher than 42% 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 7 May 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

Affected software

ProductAffectedFixed in
GitHubcxcxcxcxcxcxcxc/cxcxcxcxcxcxcxcpkg:github/cxcxcxcxcxcxcxc/cxcxcxcxcxcxcxcOther threatsAffected
  • =2.6
Fixed in–

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

AI-suggested

Until an official patch is released, organizations should implement immediate mitigations including: 1) Employing Web Application Firewalls (WAFs) with rules specifically designed to detect and block SQL injection attempts targeting the nodeTitle parameter. 2) Restricting network access to Roothub instances to trusted IP addresses and internal networks only. 3) Conducting thorough input validation and sanitization on all user-supplied data, especially parameters passed to database queries. 4) Reviewing and hardening database permissions to minimize the impact of potential SQL injection attacks, such as using least privilege principles for database accounts. 5) Monitoring logs for unusual database query patterns or errors indicative of injection attempts. 6) Preparing for rapid patch deployment once an official fix becomes available by maintaining an inventory of affected systems. 7) Considering temporary disabling or isolating vulnerable functionality if feasible. These steps go beyond generic advice by focusing on specific parameters and access controls relevant to this vulnerability.

Description

Roothub v2.6 was discovered to contain a SQL injection vulnerability via the nodeTitle parameter in the parentNode() function..

References

Community reviews

Loading reviews…