CVE-2025-7589
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-7589 is a critical SQL injection vulnerability in version 1.3 of the PHPGurukul Dairy Farm Shop Management System. It exists in the edit-company.php file, specifically in the companyname parameter. This parameter is not properly sanitized or validated, allowing attackers to inject malicious SQL code. This enables unauthorized manipulation of SQL queries, potentially leading to unauthorized data access, modification, or deletion in the database. The vulnerability can be exploited remotely and has a publicly available proof-of-concept. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can allow attackers to perform unauthorized database operations such as accessing sensitive data, modifying or deleting records, and potentially causing full system compromise or service disruption. This impacts the confidentiality, integrity, and availability of the affected system, leading to data leakage, loss of data integrity, and denial of service. [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 'companyname' parameter in the 'edit-company.php' file for SQL injection. One method is to use time-based blind SQL injection payloads, such as: companyname=Gharwal' RLIKE SLEEP(5) AND 'ysMC'='ysMC&update=, which causes a delay in response if vulnerable. Additionally, automated tools like sqlmap can be used to confirm the injection and enumerate databases. Searching for vulnerable endpoints using Google dorking with queries like inurl:edit-company.php can help identify targets. [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, enforcing strict input validation and filtering on the 'companyname' parameter to ensure inputs conform to expected formats, and minimizing database user privileges by avoiding the use of high-privilege accounts for routine database operations. Since no known countermeasures or patches are documented, replacing the affected product with an alternative is also suggested. [2, 3]