Skip to main content
VulnerabilityPublished Updated

CVE-2024-24140: Sourcecodester Daily Habit Tracker App · SQL Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 7.2 High.

Data as of 26 Oct 2026, 16:39 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Jan 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

Affected software

ProductAffectedFixed in
GitHubburaksevben/Daily_Habit_Tracker_App_SQL_Injectionpkg:github/buraksevben/Daily_Habit_Tracker_App_SQL_InjectionOther threatsAffected
  • =1.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability effectively, organizations should: 1) Immediately audit all instances of the Daily Habit Tracker App 1.0 for the presence of the vulnerable 'tracker' parameter usage. 2) Implement parameterized queries or prepared statements to eliminate direct concatenation of user input into SQL commands, thereby preventing injection. 3) Enforce strict input validation and sanitization on all user-supplied data, especially for parameters interacting with the database. 4) Restrict database user privileges to the minimum necessary, limiting the potential damage from any successful injection. 5) Monitor database and application logs for unusual query patterns or errors indicative of injection attempts. 6) If possible, upgrade to a patched version of the application or apply vendor-provided fixes once available. 7) Conduct regular security training for privileged users to reduce the risk of insider exploitation. 8) Employ Web Application Firewalls (WAFs) configured to detect and block SQL Injection payloads targeting the vulnerable parameter. These steps go beyond generic advice by focusing on the specific parameter and privilege context of this vulnerability.

Description

Sourcecodester Daily Habit Tracker App 1.0 allows SQL Injection via the parameter 'tracker.'

References

Community reviews

Loading reviews…