Skip to main content
VulnerabilityPublished Updated

CVE-2024-33161: cxcxcxcxcxcxcxc · SQL Injection

Affects cxcxcxcxcxcxcxcSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

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

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.7.0
Fixed in–

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

AI-suggested

  1. Restrict local access to systems running J2EEFAST to trusted users only, minimizing the risk of local exploitation.
  2. Implement strict input validation and sanitization on the sql_filter parameter and any other user inputs interacting with SQL queries to prevent injection.
  3. Employ the principle of least privilege for database accounts used by J2EEFAST, limiting the scope of potential damage.
  4. Monitor database logs and application behavior for unusual query patterns or errors indicative of injection attempts.
  5. Use Web Application Firewalls (WAFs) with SQL injection detection capabilities to provide an additional layer of defense.
  6. Stay alert for official patches or updates from J2EEFAST developers and apply them promptly once available.
  7. Conduct code reviews and security testing focusing on SQL injection vulnerabilities in all application inputs.
  8. Consider isolating the affected application components in segmented network zones to reduce lateral movement risk.

Description

J2EEFAST v2.7.0 was discovered to contain a SQL injection vulnerability via the sql_filter parameter in the unallocatedList() function.

References

Community reviews

Loading reviews…