CVE-2024-44659: n/a
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% 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 Nov 2025
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-26.
What to do
AI-suggested
Immediate mitigation steps include reviewing the forgot-password.php code to identify and sanitize the email parameter input. Developers should implement prepared statements or parameterized queries to prevent SQL Injection. Employing web application firewalls (WAFs) with SQL Injection detection rules can provide temporary protection while patches are developed. Conduct thorough security testing, including automated and manual code reviews, to identify similar injection points. Organizations should monitor logs for suspicious database queries or failed login attempts indicative of exploitation attempts. If PHPGurukul Online Shopping Portal 2.0 is in use, prioritize upgrading to a patched version once available or consider alternative secure platforms. Additionally, implement strict access controls and database user permissions to limit the impact of potential exploitation. Regular security awareness training for developers on secure coding practices is recommended to prevent future vulnerabilities.
Description
PHPGurukul Online Shopping Portal 2.0 is vulnerable to SQL Injection via the email parameter in forgot-password.php.