CVE-2025-7158
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-7158 is a critical SQL injection vulnerability in the PHPGurukul Zoo Management System version 2.1, specifically in the /admin/manage-normal-ticket.php file. The vulnerability occurs because the 'id' parameter is not properly sanitized or validated before being used in SQL queries. This allows attackers to inject malicious SQL code remotely, manipulating database queries arbitrarily. Exploits include time-based blind SQL injection techniques, enabling attackers to extract, modify, or delete data and potentially gain full control over the system. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing unauthorized attackers to access, modify, or delete sensitive data in your database. It threatens the confidentiality, integrity, and availability of your system. Attackers can perform unauthorized database operations, cause data leakage, tamper with records, disrupt services, and potentially take full control of the affected system, leading to significant security and business continuity risks. [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 "id" parameter in the /admin/manage-normal-ticket.php file for SQL injection flaws. Tools like sqlmap can be used to automate detection. For example, running a command such as `sqlmap -u "http://target/admin/manage-normal-ticket.php?id=1" --batch` can help identify the vulnerability. Additionally, Google dorking with the query `inurl:admin/manage-normal-ticket.php` can help locate potentially vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, performing rigorous input validation and filtering on the "id" parameter to ensure it conforms to expected formats, and minimizing database user permissions by avoiding the use of high-privilege accounts for routine operations. Since no known countermeasures or patches are documented, replacing the affected component with an alternative product is also suggested. [2, 3]