CVE-2024-55509: CSV · SQL Injection
Affects CSVSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 12:54 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 56% 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 20 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubprithivilakshmanan/CSVpkg:github/prithivilakshmanan/CSVOther 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
- Immediate network-level controls: Restrict external access to the delete.php endpoint using firewalls or web application firewalls (WAFs) with rules to detect and block SQL injection patterns targeting the 'id' parameter.
- Input validation and sanitization: Implement strict input validation on the 'id' parameter, allowing only expected numeric or alphanumeric values, and use parameterized queries or prepared statements in the backend code to prevent SQL injection.
- Monitoring and detection: Deploy intrusion detection systems (IDS) and log analysis tools to monitor for suspicious SQL injection attempts or unusual database queries related to the complaint management system.
- Segmentation: Isolate the complaint management system from critical internal networks to limit lateral movement in case of compromise.
- Vendor engagement: Contact CodeAstro for official patches or updates and apply them as soon as they become available.
- Incident response readiness: Prepare for potential exploitation by backing up data securely and having an incident response plan tailored to web application compromises.
- Temporary mitigation: If patching is delayed, consider disabling or restricting access to the delete.php component until a fix is applied.
Description
SQL injection vulnerability in CodeAstro Complaint Management System v.1.0 allows a remote attacker to execute arbitrary code and escalate privileges via the id parameter of the delete.php component.