CVE-2024-24028: n/a
Source CVE Database V5
Not known to be exploited · CVSS 5.9 Medium · fixed in 2.5.7 : update Likeshop when convenient.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Affects
- Likeshop before 2.5.7
- Patch
- Available – fixed in 2.5.7
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 29 Feb 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. 2. Implement strict input validation and sanitization on the 'avatar' parameter to ensure only allowed URLs or data formats are accepted, blocking requests to internal or non-whitelisted IP ranges. 3. Employ network segmentation and firewall rules to restrict the server's ability to make arbitrary outbound requests, especially to internal IP ranges and sensitive services like cloud metadata endpoints. 4. Use web application firewalls (WAFs) with SSRF detection capabilities to monitor and block suspicious request patterns targeting the vulnerable parameter. 5. Conduct regular security assessments and penetration tests focusing on SSRF and related vulnerabilities in the application. 6. Monitor application logs for unusual outbound requests or errors related to the avatar update functionality. 7. If patching is delayed, consider disabling or restricting the affected functionality temporarily to reduce exposure. 8. Educate developers and administrators about SSRF risks and secure coding practices to prevent similar issues in future development.
Description
Server Side Request Forgery (SSRF) vulnerability in Likeshop before 2.5.7 allows attackers to view sensitive information via the avatar parameter in function UserLogic::updateWechatInfo.