CVE-2024-48427: CVE-2024-48427 · A SQL Injection
Affects CVE-2024-48427Source CVE Database V5
Not known to be exploited · CVSS 8.1 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.9% 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:L/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 24 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubvighneshnair7/CVE-2024-48427pkg:github/vighneshnair7/CVE-2024-48427Other threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Implement strict input validation and use parameterized queries or prepared statements for all database interactions, especially for the 'id' parameter in the affected endpoint.
- Conduct a thorough code review and security audit of the entire application to identify and remediate similar injection points.
- Enforce the principle of least privilege for user accounts, ensuring that only necessary users have administrative access.
- Monitor and log database queries and administrative actions to detect unusual or unauthorized activities promptly.
- Apply web application firewalls (WAFs) with rules targeting SQL injection patterns as an additional layer of defense.
- Segregate the database and application layers with strict access controls to limit the impact of a successful injection.
- Educate administrators and users about credential security to prevent account compromise.
- Stay alert for official patches or updates from the vendor and apply them immediately upon release.
- Consider implementing multi-factor authentication (MFA) to reduce the risk of credential misuse.
- Regularly back up critical data and test restoration procedures to mitigate potential data manipulation consequences.
Description
A SQL injection vulnerability in Sourcecodester Packers and Movers Management System v1.0 allows remote authenticated users to execute arbitrary SQL commands via the id parameter in /mpms/admin/?page=services/manage_service&id