CVE-2025-7584
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-7584 is a SQL injection vulnerability in the PHPGurukul Online Fire Reporting System version 1.2, specifically in the /admin/add-team.php file. The vulnerability arises because the 'teammember' parameter is not properly sanitized or validated before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely, which can manipulate the database in unauthorized ways. [1, 2]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized database access, data leakage, data manipulation, full system control, and potential service disruption. Attackers can execute arbitrary SQL commands, which may compromise the confidentiality, integrity, and availability of the system and its data. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The vulnerability can be detected by testing the 'teammember' parameter in the /admin/add-team.php file for SQL injection. One method is to use a time-based blind SQL injection payload such as: teammember=AAA,BBB,CCC' RLIKE SLEEP(5) AND 'xQkr'='xQkr submitted via POST to observe delayed responses. Additionally, the sqlmap tool can be used to confirm and enumerate the vulnerability by targeting this parameter. [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) Enforce strict input validation and filtering on the 'teammember' parameter to ensure inputs conform to expected formats and block malicious data. 3) Restrict database user permissions to the minimum necessary, avoiding use of high-privilege accounts like 'root' or 'admin' for routine operations. [2]