Skip to main content
VulnerabilityPublished Updated

CVE-2024-53604: PHPGurukul COVID · Code Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 16:39 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 62% 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 27 Nov 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-53604, organizations should immediately implement the following specific measures: 1) Apply input validation and parameterized queries or prepared statements in the /covid-tms/check_availability.php script to sanitize the 'mobnumber' POST parameter and prevent SQL injection. 2) If source code modification is not immediately possible, deploy Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting this endpoint. 3) Restrict network access to the COVID 19 Testing Management System to trusted internal users and networks, minimizing exposure to external attackers. 4) Conduct thorough code audits and penetration testing on all PHPGurukul applications to identify and remediate similar injection flaws. 5) Monitor logs for suspicious activity related to SQL injection attempts or unusual database queries. 6) Develop and test incident response plans specific to healthcare data breaches and system compromises. 7) Coordinate with PHPGurukul or relevant vendors for official patches or updates and apply them promptly once available. 8) Educate developers and administrators on secure coding practices, especially regarding input handling and database interactions. These targeted actions go beyond generic advice and address the root cause and exploitation vectors of the vulnerability.

Description

A SQL Injection vulnerability was found in /covid-tms/check_availability.php in PHPGurukul COVID 19 Testing Management System v1.0, which allows remote attackers to execute arbitrary code via the mobnumber POST request parameter.

References

Community reviews

Loading reviews…