CVE-2024-48357: LyLme_Spage_2 · n/a
Affects LyLme_Spage_2Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubjingyi-u/LyLme_Spage_2pkg:github/jingyi-u/LyLme_Spage_2Other 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-48357, organizations should immediately restrict access to the /admin/apply.php endpoint through network segmentation and IP whitelisting to limit exposure to trusted administrators only. Deploy Web Application Firewalls (WAFs) with robust SQL Injection detection and prevention rules tailored to block malicious payloads targeting this endpoint. Conduct thorough input validation and sanitization on all user-supplied data, especially in administrative interfaces, to prevent injection of malicious SQL code. Monitor database logs and application logs for unusual query patterns or error messages indicative of injection attempts. If possible, disable or remove the vulnerable functionality until a vendor patch is released. Engage with the software vendor or community to obtain or develop patches addressing this vulnerability. Additionally, implement regular security assessments and penetration testing focused on injection flaws to proactively identify and remediate similar issues. Maintain up-to-date backups and incident response plans to recover quickly from potential exploitation.
Description
LyLme Spage 1.2.0 through 1.6.0 is vulnerable to SQL Injection via /admin/apply.php.