CVE-2025-7599
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-7599 is a critical SQL injection vulnerability in PHPGurukul Dairy Farm Shop Management System version 1.3, specifically in the /invoice.php file. The vulnerability arises because the 'del' parameter is improperly handled and directly used in SQL queries without proper sanitization or validation. This allows an attacker to inject malicious SQL code remotely, potentially manipulating the database, accessing unauthorized data, or disrupting the system. The flaw is due to CWE-89 (Improper Neutralization of Special Elements used in an SQL Command). [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to remotely execute arbitrary SQL commands on your database through the 'del' parameter in the invoice.php file. This can lead to unauthorized access to sensitive data, data leakage, data manipulation, full system control, and potential service disruption. The exploit is easy to perform and publicly available, increasing the risk of attack. The vulnerability affects the confidentiality, integrity, and availability of your system. [1, 2]
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 /invoice.php file for SQL injection. One method is to use time-based blind SQL injection payloads such as `del=OUFBQUFB' RLIKE SLEEP(5)-- qxod` to observe delays in database response. Tools like sqlmap can be used with a custom tamper script (Base64WithAppendStr) to automate detection. Additionally, Google hacking techniques like searching for `inurl:invoice.php` can help identify potentially vulnerable targets. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected software with a non-vulnerable alternative if possible. 2) Applying prepared statements with parameter binding to separate SQL code from user input. 3) Implementing strict input validation and filtering on the 'del' parameter. 4) Restricting database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. These measures help prevent SQL injection and protect system security and data integrity. [1, 2]