CVE-2025-7162
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-7162 is a critical SQL injection vulnerability in the PHPGurukul Zoo Management System version 2.1, specifically in the file /admin/add-foreigners-ticket.php. The vulnerability occurs because the 'cprice' parameter is not properly sanitized or validated before being used in SQL queries. This allows an attacker to inject malicious SQL code through the 'cprice' parameter, enabling unauthorized manipulation of the database, such as accessing, modifying, or deleting data. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing remote attackers to execute arbitrary SQL commands on the affected system. This can lead to unauthorized access to sensitive data, data leakage, data manipulation, and potentially full system compromise or service disruption. The confidentiality, integrity, and availability of the system can be severely affected. Since the exploit is publicly available and easy to exploit, the risk of active exploitation is high. [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-foreigners-ticket.php file for SQL injection. One method is to use sqlmap, an automated tool for detecting and exploiting SQL injection flaws. Additionally, a time-based blind SQL injection test can be performed by sending a POST request with a payload such as: visitorname=AAA&noadult=123&nochildren=321&aprice=1100&cprice=800' AND (SELECT SLEEP(5)) AND '1'='1&submit=. Using sqlmap, you can run a command like: sqlmap -u "http://target/admin/add-foreigners-ticket.php" --data="visitorname=AAA&noadult=123&nochildren=321&aprice=1100&cprice=800&submit=" --risk=3 --level=5 --batch to automate detection. [3, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Apply strict input validation and filtering on the 'cprice' parameter to ensure it conforms to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as 'root' or 'admin' for routine database operations. Additionally, consider replacing the affected component with an alternative product if possible, as no known mitigations are documented. [3, 2]