CVE-2025-7161
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-7161 is a critical SQL injection vulnerability in PHPGurukul Zoo Management System version 2.1, specifically in the /admin/add-normal-ticket.php file. The vulnerability arises because the 'cprice' parameter is used directly in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code remotely. This can lead to unauthorized manipulation of database queries and execution of arbitrary database operations. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can allow attackers to manipulate SQL queries, leading to unauthorized database access, data leakage, data tampering, full system compromise, and service disruption. This poses severe risks to system security and business continuity by compromising the confidentiality, integrity, and availability of the affected 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 'cprice' parameter in the /admin/add-normal-ticket.php file for SQL injection. One method is to use time-based blind SQL injection payloads, such as injecting a payload that uses the SLEEP() function to observe delays in response time. For example, sending a POST request with cprice=80' AND (SELECT 5394 FROM (SELECT(SLEEP(5)))TaDy) AND 'mjhB'='mjhB can confirm the vulnerability if the response is delayed. Tools like sqlmap can also be used to automate detection by targeting the 'cprice' parameter. Additionally, attackers may identify vulnerable targets using Google dorking with queries like "inurl:admin/add-normal-ticket.php" to find instances of the affected system. [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 inputs, thereby preventing SQL injection. Enforce strict input validation and filtering on the 'cprice' parameter to ensure inputs conform to expected formats and block malicious data. Additionally, minimize database user privileges by avoiding the use of high-privilege accounts such as root or admin for routine database operations. Since no known mitigations or countermeasures have been documented for this specific vulnerability, replacing the affected component with an alternative product is also recommended. [2, 3]