Skip to main content
VulnerabilityPublished Updated

CVE-2024-40456: ThinkSAAS · SQL Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 13:47 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 43% 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 16 Jul 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

AI-suggested

To mitigate CVE-2024-40456, organizations should first verify if they are running ThinkSAAS version 3.7.0 and prioritize upgrading to a patched version once available. In the absence of an official patch, implement strict input validation and sanitization on the 'name' parameter to prevent malicious SQL code injection. Employ parameterized queries or prepared statements in the application code to eliminate direct concatenation of user input into SQL commands. Deploy Web Application Firewalls (WAFs) with rules specifically designed to detect and block SQL injection attempts targeting the vulnerable endpoint. Conduct thorough security audits and penetration testing focused on SQL injection vectors within ThinkSAAS. Monitor database logs and application behavior for unusual queries or access patterns indicative of exploitation attempts. Restrict database user privileges to the minimum necessary to limit the impact of a successful injection. Finally, establish an incident response plan to quickly address any detected exploitation.

Description

ThinkSAAS v3.7.0 was discovered to contain a SQL injection vulnerability via the name parameter at \system\action\update.php.

References

Community reviews

Loading reviews…