CVE-2025-7160
BaseFortify
Publication date: 2025-07-08
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 | zoo_management_system | 2.1 |
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-7160 is a critical SQL injection vulnerability in the PHPGurukul Zoo Management System version 2.1, specifically in the /admin/index.php file. The vulnerability occurs because the 'username' parameter is directly used in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code. This enables attackers to manipulate SQL queries arbitrarily and perform unauthorized database operations remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized data access, data leakage, data tampering, and potentially full control over the affected system or disruption of services. Since the attack can be performed remotely without authentication, it poses a high risk to 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 "username" parameter in POST requests to /admin/index.php for SQL injection. Tools like sqlmap can be used to automate detection. Example commands include: 1. Using sqlmap: sqlmap -u "http://target/admin/index.php" --data="username=admin&password=any" -p username --batch 2. Manual testing with payloads: - Boolean-based test: username=admin' AND 7462=7462-- - Time-based test: username=admin' AND (SELECT SLEEP(5))-- Additionally, Google dorking with queries like inurl:admin/index.php can help identify vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1. Implement prepared statements with parameter binding to prevent SQL injection. 2. Apply strict input validation and filtering on the "username" parameter to ensure only expected input is accepted. 3. Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as 'root' or 'admin' for routine operations. 4. If possible, replace the affected software with an alternative solution as no known mitigations are documented. These steps help prevent exploitation and reduce the impact of the vulnerability. [2, 3]