CVE-2025-5612: PHPGurukul Online Fire Reporting System · SQL Injection
Affects PHPGurukul Online Fire Reporting SystemSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubphpgurukul/Online_Fire_Reporting_Systempkg:github/phpgurukul/Online_Fire_Reporting_SystemOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate this vulnerability, organizations should immediately review and update the input validation and sanitization mechanisms for all parameters in the /reporting.php file, especially the 'fullname' parameter. Implementing parameterized queries or prepared statements is essential to prevent SQL injection attacks. If a patch from the vendor becomes available, it should be applied promptly. In the absence of an official patch, organizations should consider deploying Web Application Firewalls (WAFs) with specific rules to detect and block SQL injection payloads targeting the affected endpoints. Regular code audits and penetration testing should be conducted to identify and remediate similar injection flaws. Additionally, monitoring database logs for suspicious queries and implementing strict access controls on the database can help detect and limit the impact of potential exploitation. Finally, organizations should ensure that backups of critical data are maintained securely to enable recovery in case of data tampering.
Description
A vulnerability has been found in PHPGurukul Online Fire Reporting System 1.2 and classified as critical. This vulnerability affects unknown code of the file /reporting.php. The manipulation of the argument fullname leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. Other parameters might be affected as well.