CVE-2025-7563
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 | online_fire_reporting_system | 1.2 |
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-7563 is a critical SQL injection vulnerability in PHPGurukul Online Fire Reporting System version 1.2. It exists in the /admin/completed-requests.php file, specifically involving the 'teamid' parameter. This parameter is not properly sanitized or validated before being used in SQL queries, allowing attackers to inject malicious SQL code. This can lead to unauthorized manipulation of the database, including unauthorized access, data leakage, and data manipulation. The vulnerability can be exploited remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can allow attackers to perform unauthorized database operations such as accessing sensitive data, modifying or deleting data, and potentially gaining full control over the system. It can also lead to service disruption. Because the vulnerability can be exploited remotely without authentication and a proof-of-concept exploit is publicly available, the risk to affected systems is significant, potentially impacting system security and business continuity. [1, 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 'teamid' parameter in the /admin/completed-requests.php file for SQL injection. A time-based blind SQL injection test can be performed using a payload such as `teamid=1' RLIKE SLEEP(5)-- voJn` to observe if the database response is delayed, indicating vulnerability. Tools like sqlmap can be used to automate detection by targeting the 'teamid' parameter for injection testing. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Using prepared statements with parameter binding to separate SQL code from user input, preventing SQL injection. 2) Implementing strict input validation and filtering on the 'teamid' parameter to ensure inputs conform to expected formats. 3) Limiting database user permissions by avoiding high-privilege accounts for routine operations to reduce exploit impact. Additionally, replacing the affected software with an alternative product is suggested as no known countermeasures are documented. [2, 3]