CVE-2024-50724: KASO-SQL · SQL Injection
Affects KASO-SQLSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% 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 15 Nov 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 |
|---|---|---|
GitHubyouyuzhongli/KASO-SQLpkg:github/youyuzhongli/KASO-SQLOther 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
To mitigate CVE-2024-50724, organizations should immediately implement the following measures: 1) Apply input validation and sanitization on the person_id parameter to reject or properly encode malicious input. 2) Refactor database queries to use parameterized statements or prepared queries to prevent SQL injection. 3) Employ web application firewalls (WAFs) with rules targeting SQL injection patterns, specifically monitoring requests to /cardcase/editcard.jsp. 4) Conduct thorough code audits of the affected application components to identify and remediate similar injection flaws. 5) Restrict database user privileges to the minimum necessary to limit the impact of potential exploitation. 6) Monitor database logs and application logs for unusual query patterns or errors indicative of injection attempts. 7) If possible, isolate or segment the affected application environment to reduce lateral movement risk. 8) Engage with the vendor or development team to obtain patches or updates as soon as they become available. 9) Educate developers on secure coding practices to prevent future injection vulnerabilities. These steps go beyond generic advice by focusing on immediate technical controls and proactive monitoring tailored to this vulnerability.
Description
KASO v9.0 was discovered to contain a SQL injection vulnerability via the person_id parameter at /cardcase/editcard.jsp.