CVE-2024-24496: n/a
Source CVE Database V5
Not known to be exploited · public exploit available (Exploit-DB) · 19% EPSS · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 19.5% chance of exploitation in 30 days – higher than 97% 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
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 8 Feb 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
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
Timeline
CVE ID reserved
by MITRE Corporation
, 14 days before disclosure
CVE published
on cve.org
, t = 0
First Exploit-DB entry (opens in a new tab)
Daily Habit Tracker 1.0 - Broken Access Control
, 54 days after disclosure
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-24496, organizations should immediately restrict access to the affected PHP endpoints (home.php, add-tracker.php, delete-tracker.php, update-tracker.php) using network-level controls such as firewalls or VPNs. Implement strong authentication mechanisms to ensure only authorized users can access these components. Enforce strict authorization checks to validate user permissions before allowing any data manipulation. Conduct a thorough code review to identify and fix authentication and authorization flaws. Monitor application logs for unusual activity related to tracker manipulation. If possible, isolate the application from the internet until a vendor patch is available. Regularly back up tracker data to enable recovery in case of data tampering. Engage with the vendor for timely patch releases and apply updates as soon as they become available. Consider deploying web application firewalls (WAF) with custom rules to detect and block exploitation attempts targeting these endpoints.
Description
An issue in Daily Habit Tracker v.1.0 allows a remote attacker to manipulate trackers via the home.php, add-tracker.php, delete-tracker.php, update-tracker.php components.