CVE-2024-40392: SQL Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 12:54 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 42% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 16 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-40392, organizations should immediately implement the following measures: 1) Apply input validation and sanitization on all user-supplied data, especially the 'name' parameter in addnew.php, to prevent injection of malicious SQL code. 2) Refactor database queries to use parameterized prepared statements or stored procedures to eliminate direct concatenation of user input into SQL commands. 3) Restrict database user permissions to the minimum necessary, avoiding use of highly privileged accounts for application database connections. 4) Monitor database logs and application behavior for unusual queries or access patterns indicative of exploitation attempts. 5) If patching from the vendor becomes available, prioritize timely deployment. 6) Consider deploying Web Application Firewalls (WAFs) with SQL injection detection rules as an interim protective measure. 7) Conduct security code reviews and penetration testing to identify and remediate similar vulnerabilities in other parts of the application. 8) Educate development teams on secure coding practices to prevent recurrence.
Description
SourceCodester Pharmacy/Medical Store Point of Sale System Using PHP/MySQL and Bootstrap Framework with Source Code 1.0 was discovered to contain a SQL injection vulnerability via the name parameter under addnew.php.