Skip to main content
CVE-2024-33144VulnerabilityPublished Updated

CVE-2024-33144: cxcxcxcxcxcxcxc · n/a

Affects cxcxcxcxcxcxcxcSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 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 44% 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 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

Organizations should immediately audit their use of J2EEFAST 2.7.0 and identify affected components using the findApplyedTasksPage function. Since no official patches are currently available, implement strict input validation and sanitization on the sql_filter parameter to prevent injection of malicious SQL code. Refactor the code to use parameterized queries or prepared statements instead of dynamic SQL construction. Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting this parameter. Monitor database logs and application behavior for unusual queries or errors indicative of exploitation attempts. Restrict database user privileges to the minimum necessary to limit the impact of any successful injection. Stay alert for vendor updates or patches and apply them promptly once released. Conduct penetration testing focused on SQL injection vectors to validate the effectiveness of mitigations.

Description

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

References

Community reviews

Loading reviews…