CVE-2025-51970: SQL Injection
Source CVE Database V5
Not known to be exploited · CVSS 7.7 High.
Data as of 26 Oct 2026, 09:08 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Jul 2025
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
Given the absence of an official patch, European organizations should implement immediate compensating controls. These include restricting local access to the affected systems through network segmentation and strict access controls, ensuring only trusted personnel can reach the vulnerable endpoint. Employing Web Application Firewalls (WAFs) with custom rules to detect and block SQL Injection patterns targeting the 'keyword' POST parameter can reduce exploitation risk. Conduct thorough input validation and sanitization on all user inputs, ideally by applying parameterized queries or prepared statements in the application code. Organizations should also monitor logs for suspicious activity around the action.php endpoint and the keyword parameter. Regularly auditing user privileges and employing intrusion detection systems (IDS) can help detect lateral movement attempts. Finally, organizations should engage with the vendor or development team to prioritize patch development and apply updates promptly once available.
Description
A SQL Injection vulnerability exists in the action.php endpoint of PuneethReddyHC Online Shopping System Advanced 1.0 due to improper sanitization of user-supplied input in the keyword POST parameter.