CVE-2024-54811: A 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.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 12 Dec 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-54811, organizations should immediately implement the following measures: 1) Apply strict input validation and sanitization on the 'login' parameter and all user inputs, preferably using prepared statements or parameterized queries to prevent SQL injection. 2) Deploy a Web Application Firewall (WAF) configured to detect and block SQL injection patterns targeting the vulnerable endpoint. 3) Conduct thorough code reviews and security testing of the PHPGurukul Park Ticketing Management System, focusing on SQL query construction and user input handling. 4) Monitor database logs and web server logs for unusual or suspicious query patterns indicative of injection attempts. 5) Isolate the ticketing system within a segmented network zone to limit lateral movement in case of compromise. 6) Regularly back up critical data and verify restoration procedures to minimize impact from potential data corruption or deletion. 7) Engage with the software vendor or community to track the release of official patches and apply them promptly once available. 8) Consider temporary mitigation by restricting access to the vulnerable endpoint via IP whitelisting or VPN until a patch is deployed.
Description
A SQL injection vulnerability in /index.php in PHPGurukul Park Ticketing Management System v1.0 allows an attacker to execute arbitrary SQL commands via the "login" parameter.