CVE-2025-7582
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-7582 is a critical SQL injection vulnerability in PHPGurukul Online Fire Reporting System version 1.2. It occurs in the /admin/assigned-requests.php file due to improper handling of the 'teamid' parameter, which is used directly in SQL queries without proper sanitization or validation. This allows attackers to inject malicious SQL code remotely, enabling unauthorized database access, data leakage, data manipulation, and potentially full system control or service disruption. [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 without authentication. This can lead to unauthorized access to sensitive data, data leakage, data manipulation, disruption of service, and potentially full control over the system. The exploit is easy to perform and publicly available, increasing the risk of exploitation. [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/assigned-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)-- which causes a delay in the database response if vulnerable. Additionally, the sqlmap tool can be used to automate detection with a command targeting the 'teamid' parameter to enumerate databases. [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 injection; 2) Implementing strict input validation and filtering to ensure inputs conform to expected formats and block malicious data; 3) Limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as 'root' or 'admin' for routine operations. If possible, replacing the affected software with an alternative product is also suggested. [2, 3]