Skip to main content
VulnerabilityPublished Updated

CVE-2024-24095: Code-projects Simple Stock System · SQL Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% 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 Feb 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-24095, organizations should first implement immediate input validation and sanitization on all user-supplied data fields interacting with the database. Employ parameterized queries or prepared statements to ensure SQL commands are not constructed with direct user input. If possible, restrict database user permissions to the minimum required to limit damage in case of exploitation. Network-level controls such as web application firewalls (WAFs) can be configured to detect and block common SQL injection patterns. Conduct thorough code reviews and security testing focusing on injection flaws. Monitor database logs and application behavior for unusual queries or access patterns indicative of exploitation attempts. Organizations should also plan for patch management and update the software once a vendor-provided fix becomes available. In the interim, consider isolating the affected system from critical network segments to reduce attack surface. Educate development and IT teams on secure coding and incident response procedures related to injection vulnerabilities.

Description

Code-projects Simple Stock System 1.0 is vulnerable to SQL Injection.

References

Community reviews

Loading reviews…