CVE-2025-51672: Dairy-Farm-Shop-Management-System · SQL Injection
Affects Dairy-Farm-Shop-Management-SystemSource CVE Database V5
Not known to be exploited · CVSS 8.0 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Jun 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubrtnthakur/Dairy-Farm-Shop-Management-Systempkg:github/rtnthakur/Dairy-Farm-Shop-Management-SystemOther 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
European organizations should immediately conduct a thorough security assessment of any PHPGurukul Dairy Farm Shop Management System deployments. Specific mitigations include: 1) Implement strict input validation and parameterized queries or prepared statements in the 'manage-companies.php' file to prevent SQL injection. 2) Restrict access to the management system to trusted internal networks or VPNs to reduce exposure. 3) Monitor and analyze web server logs for unusual POST requests targeting the 'companyname' parameter to detect potential exploitation attempts. 4) Employ Web Application Firewalls (WAFs) with rules designed to detect and block SQL injection patterns, particularly time-based blind techniques. 5) Regularly back up databases and test restoration procedures to mitigate data loss risks. 6) Engage with PHPGurukul or the software vendor to obtain patches or updates addressing this vulnerability as soon as they become available. 7) Conduct user training to recognize and report suspicious system behavior. These steps go beyond generic advice by focusing on the specific vulnerable parameter and the operational context of the affected system.
Description
A time-based blind SQL injection vulnerability was identified in the PHPGurukul Dairy Farm Shop Management System 1.3. The vulnerability exists in the manage-companies.php file and allows remote attackers to execute arbitrary SQL code via the companyname parameter in a POST request.