CVE-2025-7590
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-7590 is a critical SQL injection vulnerability in version 1.3 of the PHPGurukul Dairy Farm Shop Management System. It exists in the edit-category.php file, specifically in the categorycode parameter, which is incorporated into SQL queries without proper sanitization or validation. This allows attackers to inject malicious SQL code remotely, potentially manipulating database queries unauthorizedly. [1, 2]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, leakage of sensitive data, data tampering, full system compromise, and potential service disruption. This poses significant risks to system security and business continuity. [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 'categorycode' parameter in the 'edit-category.php' file for SQL injection. A proof-of-concept uses a time-based blind SQL injection payload such as: category=Panner&categorycode=PN01' RLIKE SLEEP(5) AND 'ZVmr'='ZVmr&update= to observe delays indicating injection. Additionally, the sqlmap tool can be used to automate detection targeting the 'categorycode' parameter. [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 on the 'categorycode' parameter, and minimizing database user privileges by avoiding high-privilege accounts for routine operations. [2]