Skip to main content
VulnerabilityPublished Updated

CVE-2024-33147: cxcxcxcxcxcxcxc · SQL Injection

Affects cxcxcxcxcxcxcxcSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/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.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

To mitigate CVE-2024-33147, organizations should first verify if they are using J2EEFAST version 2.7.0 and assess exposure of the authRoleList function. Since no official patches are currently available, immediate steps include implementing strict input validation and sanitization on the sql_filter parameter to prevent injection of malicious SQL code. Refactoring the affected code to use parameterized queries or prepared statements is critical to eliminate direct concatenation of user input into SQL commands. Database user accounts used by the application should have the minimum necessary privileges, restricting capabilities to reduce potential damage from exploitation. Network-level controls such as web application firewalls (WAFs) can be configured to detect and block SQL injection attempts targeting the vulnerable parameter. Continuous monitoring and logging of database queries and application logs can help detect suspicious activity early. Organizations should stay alert for vendor patches or updates and apply them promptly once released. Additionally, conducting security code reviews and penetration testing focused on injection flaws can help identify and remediate similar vulnerabilities.

Description

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

References

Community reviews

Loading reviews…