Skip to main content
CVE-2024-33149VulnerabilityPublished Updated

CVE-2024-33149: cxcxcxcxcxcxcxc · n/a

Affects cxcxcxcxcxcxcxcSource CVE Database V5

0

Not known to be exploited · CVSS 8.1 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/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-33149, organizations should immediately audit their use of J2EEFAST 2.7.0 and identify any instances where the sql_filter parameter is used in the myProcessList function. Until an official patch is released, implement strict input validation and sanitization on all user-supplied inputs, especially sql_filter, to reject or neutralize malicious SQL syntax. Employ parameterized queries or prepared statements to prevent direct injection of user input into SQL commands. Enable and monitor database activity logging to detect unusual queries or access patterns indicative of exploitation attempts. Restrict network access to the affected application components using firewalls or network segmentation to limit exposure. Conduct regular security assessments and penetration testing focused on SQL injection vulnerabilities. Stay informed about vendor updates and apply patches promptly once available. Additionally, consider deploying web application firewalls (WAFs) with rules targeting SQL injection attempts as an interim protective measure.

Description

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

References

Community reviews

Loading reviews…