CVE-2024-30990: SQL Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 12:29 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% 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 17 Apr 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-30990, organizations should immediately implement the following measures: 1) Apply input validation and sanitization on the "searchdata" parameter to reject or properly encode malicious input. 2) Refactor the application code to use prepared statements or parameterized queries instead of directly embedding user input in SQL commands. 3) Restrict database user permissions to the minimum necessary, preventing unauthorized data modification or schema changes. 4) Monitor web application logs for suspicious query patterns or error messages indicative of injection attempts. 5) If possible, isolate the affected application in a segmented network zone to limit potential lateral movement. 6) Engage with the vendor or community to obtain patches or updates as soon as they become available. 7) Conduct security testing, including automated scanning and manual code review, to identify and remediate similar injection flaws elsewhere in the application. 8) Educate developers on secure coding practices to prevent future injection vulnerabilities. These steps go beyond generic advice by focusing on immediate code-level fixes, privilege restrictions, and proactive monitoring tailored to this specific vulnerability.
Description
SQL Injection vulnerability in the "Invoices" page in phpgurukul Client Management System using PHP & MySQL 1.1 allows attacker to execute arbitrary SQL commands via "searchdata" parameter.