CVE-2024-48356: LyLme_Spage · SQL Injection
Affects LyLme_SpageSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% 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 28 Oct 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 |
|---|---|---|
GitHubjingyi-u/LyLme_Spagepkg:github/jingyi-u/LyLme_SpageOther 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
- Immediately monitor official LyLme Spage channels for security patches or updates addressing CVE-2024-48356 and apply them as soon as they become available.
- Until a patch is released, implement strict input validation and sanitization on all user inputs, particularly those interacting with /admin/group.php, to block SQL injection payloads.
- Deploy Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the vulnerable endpoint.
- Restrict network access to the /admin/group.php interface to trusted IP addresses or VPN users to reduce exposure.
- Conduct thorough code reviews and penetration testing focusing on SQL injection vulnerabilities in all web application components.
- Monitor logs for unusual database queries or error messages indicative of attempted exploitation.
- Educate development teams on secure coding practices to prevent similar vulnerabilities in future releases.
- Consider isolating or segmenting the affected application environment to limit potential lateral movement if compromised.
Description
LyLme Spage <=1.6.0 is vulnerable to SQL Injection via /admin/group.php.