CVE-2024-25247: SQL Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 12:54 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:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 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 26 Oct 2026.
What to do
AI-suggested
To mitigate CVE-2024-25247, organizations should immediately review and sanitize all inputs, especially the latitude and longitude parameters in the Store.php controller. Implement parameterized queries or prepared statements to prevent SQL injection. If patches become available from Niushop, apply them promptly. In the absence of official patches, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting these parameters. Conduct thorough code audits for similar injection flaws in other parts of the application. Monitor database logs and application behavior for unusual queries or access patterns. Restrict database user privileges to the minimum necessary to limit the impact of potential exploitation. Regularly back up databases and test restoration procedures to minimize downtime in case of compromise. Finally, educate development teams on secure coding practices to prevent future injection vulnerabilities.
Description
SQL Injection vulnerability in /app/api/controller/Store.php in Niushop B2B2C V5 allows attackers to run arbitrary SQL commands via latitude and longitude parameters.