CVE-2025-5612
BaseFortify
Publication date: 2025-06-04
Last updated on: 2025-06-06
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-5612 is a critical SQL Injection vulnerability in the PHPGurukul Online Fire Reporting System version 1.2, specifically in the /reporting.php file. The vulnerability occurs because the 'fullname' parameter is not properly sanitized, allowing an attacker to inject malicious SQL code. This can enable unauthorized manipulation of the backend database, such as data leakage or unauthorized data modification, by crafting special input that alters the intended SQL queries. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by compromising the confidentiality, integrity, and availability of the affected system. An attacker can remotely exploit the flaw to access, modify, or delete sensitive data in the database without authorization. This could lead to data breaches, loss of data integrity, and potential disruption of services relying on the affected system. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of the vulnerable PHPGurukul Online Fire Reporting System version 1.2, specifically the /reporting.php file. One detection method is to use Google dorking with the query "inurl:reporting.php" to identify potentially vulnerable targets. Additionally, testing the 'fullname' parameter for SQL injection by sending crafted input and observing the response can help detect the vulnerability. For example, using curl or similar tools to send payloads that include SQL injection attempts to the fullname parameter and checking for database error messages or unexpected behavior can be effective. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected PHPGurukul Online Fire Reporting System version 1.2 with an alternative product, as no known countermeasures or patches are currently available. Additionally, restricting access to the /reporting.php file, implementing web application firewalls (WAF) to block SQL injection attempts, and monitoring for suspicious activity targeting the fullname parameter can help reduce risk until a secure version or patch is available. [2]