CVE-2024-30985: n/a
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% 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 2026-10-25.
What to do
AI-suggested
To mitigate CVE-2024-30985, organizations should immediately implement input validation and parameterized queries or prepared statements for all database interactions involving user-supplied input, specifically the "todate" and "fromdate" parameters. Employing a web application firewall (WAF) with SQL Injection detection rules can provide temporary protection until a proper patch is available. Conduct a thorough code review of the application to identify and remediate other potential injection points. Restrict database user privileges to the minimum necessary to limit the impact of any injection exploit. Monitor logs for suspicious query patterns or unusual database activity. If possible, isolate the vulnerable application from critical network segments. Engage with the vendor or community to obtain or develop a patch, and apply it promptly once released. Educate developers on secure coding practices to prevent similar vulnerabilities in future releases.
Description
SQL Injection vulnerability in "B/W Dates Reports" page in phpgurukul Client Management System using PHP & MySQL 1.1 allows attacker to execute arbitrary SQL commands via "todate" and "fromdate" parameters.