CVE-2024-48580: Best courier management system · SQL Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 59% 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 25 Oct 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-48580, organizations should immediately implement input validation and sanitization on the 'email' parameter and all user inputs. Employ parameterized queries or prepared statements to prevent SQL injection attacks. If possible, restrict access to the login endpoint via network-level controls such as firewalls or VPNs. Monitor logs for suspicious login attempts or unusual database queries. Conduct a thorough security audit of the courier management system and related infrastructure. Since no official patches are available, consider isolating the affected system and applying web application firewalls (WAF) with SQL injection detection rules. Engage with the vendor or development team to obtain or develop a patch. Regularly back up data and test restoration procedures to minimize impact from potential exploitation.
Description
SQL Injection vulnerability in Best courier management system in php v.1.0 allows a remote attacker to execute arbitrary code via the email parameter of the login request.