CVE-2025-7591
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-7591 is a critical SQL injection vulnerability in the PHPGurukul Dairy Farm Shop Management System version 1.3. It exists in the file view-invoice.php, specifically through the 'invid' parameter, which is used directly in SQL queries without proper sanitization or validation. This allows attackers to inject malicious SQL code remotely, manipulate database queries, and perform unauthorized database operations. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized database access, resulting in sensitive data leakage, data tampering, full system compromise, and potential service disruption. This severely impacts system security and business continuity by compromising the confidentiality, integrity, and availability of the system. [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 'invid' GET parameter in the 'view-invoice.php' file for SQL injection. Example commands include using SQL injection payloads such as time-based blind SQL injection with MySQL's SLEEP function or UNION-based SQL injection to extract data. For instance, you can test with curl or a browser by appending payloads like: - Time-based: invid=NDY0NzYwMzQ2NTM5MzA=' AND (SELECT 9859 FROM (SELECT(SLEEP(5)))jiBh)-- - UNION-based: invid=NDY0NzYwMzQ2NTM5MzA=' UNION ALL SELECT NULL,NULL,NULL,NULL,CONCAT(0x716a627a71,0x46654a78434c69676a46544a73466b6c624f54465841584879416e74554d4776687a775477514343,0x7178627671)-- Additionally, automated tools like sqlmap can be used with custom tamper scripts (e.g., Base64WithAppendStr) to detect and exploit the vulnerability. [2]
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. - Enforcing strict input validation and filtering to ensure inputs conform to expected formats. - Restricting database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. If possible, replace the affected software with a secure alternative or update to a fixed version once available. [2, 3]