Skip to main content
CVE-2024-33276VulnerabilityPublished Updated

CVE-2024-33276: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in 3.1.1 : patch affected systems as a priority.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.1.1
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 29 Apr 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-26.

What to do

AI-suggested

If you cannot patch yet, organizations should implement the following specific mitigations: 1) Restrict database user permissions to the minimum necessary, preventing the application from executing arbitrary SQL commands beyond its scope. 2) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the vulnerable method. 3) Conduct thorough input validation and sanitization at the application layer, especially for parameters passed to PreorderModel::getIdProductAttributesByIdAttributes(). 4) Monitor database logs and application logs for unusual queries or error messages indicative of injection attempts. 5) If feasible, isolate the affected module or disable its functionality temporarily to reduce attack surface. 6) Prepare for rapid deployment of patches once available by maintaining an inventory of affected systems and testing patch compatibility in advance. 7) Educate development teams on secure coding practices to prevent similar vulnerabilities in future releases.

Description

SQL Injection vulnerability in FME Modules preorderandnotication v.3.1.0 and before allows a remote attacker to run arbitrary SQL commands via the PreorderModel::getIdProductAttributesByIdAttributes() method.

References

Community reviews

Loading reviews…