CVE-2025-7562
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-7562 is a critical SQL injection vulnerability in PHPGurukul Online Fire Reporting System version 1.2. It exists in the /admin/new-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 remotely. This can lead to unauthorized database operations such as data leakage, tampering, or full system control. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by compromising the confidentiality, integrity, and availability of your system. Attackers can exploit it remotely without authentication to perform unauthorized database operations, including data leakage, data tampering, full system control, and potential service disruption. The exploit is easy to perform and publicly available, increasing the risk of attack. [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/new-requests.php file for SQL injection. One method is to use sqlmap, a popular automated SQL injection tool, to scan the target URL. For example, you can run: sqlmap -u "http://targetsite/admin/new-requests.php?teamid=1" --batch. Additionally, a proof-of-concept payload for time-based blind SQL injection is: teamid=1' RLIKE SLEEP(5)-- xupV, which can be tested manually or with tools to observe response delays indicating injection. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected software with an alternative product, as no known countermeasures are documented; 2) Implementing prepared statements with parameter binding to separate SQL code from user input; 3) Applying strict input validation and filtering on the 'teamid' parameter; 4) Limiting database user permissions to the minimum necessary to reduce impact; and 5) Avoiding use of high-privilege accounts for routine database operations. These steps help prevent exploitation and protect system security and data integrity. [2, 3]