Skip to main content
CVE-2024-33153VulnerabilityPublished Updated

CVE-2024-33153: cxcxcxcxcxcxcxc · n/a

Affects cxcxcxcxcxcxcxcSource 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.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: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 2026-10-25.

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-33153, organizations should immediately audit their use of J2EEFAST 2.7.0 and identify any instances of the vulnerable commentList() function. Until an official patch is released, apply the following specific measures: 1) Implement strict input validation and sanitization on the sql_filter parameter to reject or escape malicious SQL syntax; 2) Refactor the code to use parameterized queries or prepared statements to prevent direct SQL injection; 3) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the sql_filter parameter; 4) Monitor database logs for unusual queries or access patterns indicative of exploitation attempts; 5) Restrict database user privileges to the minimum necessary to limit the impact of a successful injection; 6) Consider temporary disabling or restricting access to the vulnerable commentList() functionality if feasible; 7) Stay alert for official patches or updates from the J2EEFAST maintainers and apply them immediately upon release. These targeted actions go beyond generic advice and focus on the specific vulnerable component and parameter.

Description

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

References

Community reviews

Loading reviews…