CVE-2024-22628: n/a
Source CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 16 Jan 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 2026-10-26.
What to do
AI-suggested
1. Immediate mitigation should include restricting access to the administrative interface to trusted IP addresses or VPNs to limit exposure. 2. Implement web application firewall (WAF) rules specifically designed to detect and block SQL Injection attempts targeting the vulnerable endpoint parameters. 3. Conduct thorough input validation and parameterized query implementation in the affected codebase to eliminate injection vectors. 4. Monitor logs for unusual database query patterns or failed injection attempts to detect early exploitation attempts. 5. If possible, isolate the Budget and Expense Tracker System from critical network segments until a patch or fix is available. 6. Engage with the software vendor or development team to obtain or develop a security patch addressing the vulnerability. 7. Educate administrative users on the risks and encourage the use of strong authentication methods to reduce the risk of privilege escalation. 8. Regularly back up financial data and test restoration procedures to minimize impact in case of a successful attack.
Description
Budget and Expense Tracker System v1.0 is vulnerable to SQL Injection via /expense_budget/admin/?page=reports/budget&date_start=2023-12-28&date_end=