CVE-2025-7583
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
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 input, enforcing strict input validation and filtering on the 'teamid' parameter to ensure only expected formats are accepted, and restricting 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 recommended. [2, 3]
Can you explain this vulnerability to me?
CVE-2025-7583 is a critical SQL injection vulnerability in the PHPGurukul Online Fire Reporting System version 1.2. It exists in the /admin/all-requests.php file, specifically involving the 'teamid' parameter. This parameter is used directly in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code. Exploiting this flaw enables attackers to manipulate SQL queries and perform unauthorized database operations remotely. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data manipulation, and potentially full system compromise. Attackers can exploit it remotely to affect the confidentiality, integrity, and availability of the system. It can severely impact system security and business continuity by allowing attackers to execute arbitrary SQL commands on the backend database. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending crafted HTTP GET requests to the vulnerable endpoint /admin/all-requests.php with manipulated 'teamid' parameters to test for SQL injection. A known proof-of-concept payload is: teamid=1' RLIKE SLEEP(5)-- XxJV, which uses a time-based blind SQL injection technique to observe response delays indicating vulnerability. Detection can be performed using tools like curl or Burp Suite to send such requests and monitor response times. Additionally, Google dorking with queries like inurl:admin/all-requests.php can help locate potentially vulnerable targets. [2, 3]