CVE-2024-33155: cxcxcxcxcxcxcxc · SQL Injection
Affects cxcxcxcxcxcxcxcSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 7 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
GitHubcxcxcxcxcxcxcxc/cxcxcxcxcxcxcxcpkg:github/cxcxcxcxcxcxcxc/cxcxcxcxcxcxcxcOther threats | Affected
| 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-33155, organizations should immediately audit and sanitize all inputs to the getDeptList() function, especially the sql_filter parameter. Implement parameterized queries or prepared statements to prevent SQL injection. If an official patch becomes available, apply it promptly. In the absence of a patch, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the vulnerable parameter. Conduct thorough code reviews and penetration testing focused on SQL injection vectors. Monitor database logs and application behavior for unusual queries or access patterns indicative of exploitation attempts. Restrict database user permissions to the minimum necessary to limit the impact of any successful injection. Educate developers on secure coding practices to prevent similar vulnerabilities in future releases.
Description
J2EEFAST v2.7.0 was discovered to contain a SQL injection vulnerability via the sql_filter parameter in the getDeptList() function.