CVE-2025-7592
BaseFortify
Publication date: 2025-07-14
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| phpgurukul | dairy_farm_shop_management_system | 1.3 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-7592 is a critical SQL injection vulnerability in version 1.3 of the PHPGurukul Dairy Farm Shop Management System. It exists in the invoices.php file, specifically through the 'del' parameter, which is not properly sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely, manipulating database queries arbitrarily and potentially gaining unauthorized access to or control over the database. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized database access, data leakage, data tampering, full system control, and potential service disruption. Attackers can execute arbitrary SQL commands remotely without authentication, compromising the confidentiality, integrity, and availability of the system and its data. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'del' parameter in the invoices.php file for SQL injection. A proof-of-concept time-based blind SQL injection payload is: del=OUFBQUFB' RLIKE SLEEP(5)-- which causes a delay in the database response if vulnerable. Additionally, automated tools like sqlmap can be used with custom tamper scripts to detect the injection. Searching for vulnerable targets can also be done using Google dorking with queries like "inurl:invoices.php" to identify potentially affected systems. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, applying rigorous input validation and filtering to ensure data conforms to expected formats, and minimizing database user privileges by avoiding the use of high-privilege accounts for routine operations. Since no known mitigations or countermeasures are documented, it is also recommended to replace the affected software with an alternative product to avoid exploitation. [2, 3]