CVE-2025-7559: 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, 07:57 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% 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:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 14 Jul 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PHPGurukul Online Fire Reporting System | Affected
| Fixed in– |
AI-suggested
Organizations using PHPGurukul Online Fire Reporting System version 1.2 should immediately assess their exposure and apply patches or updates if available. In the interim, implement strict input validation and sanitization on the 'fromdate' and 'todate' parameters to prevent SQL injection. Employ Web Application Firewalls (WAFs) with rules targeting SQL injection patterns to detect and block malicious requests. Restrict access to the administrative interface by IP whitelisting or VPN access to reduce exposure. Conduct regular security audits and database activity monitoring to detect anomalous queries. Finally, ensure database accounts used by the application have the least privileges necessary to limit the impact of any successful injection.
Description
A vulnerability was found in PHPGurukul Online Fire Reporting System 1.2. It has been classified as critical. This affects an unknown part of the file /admin/bwdates-report-result.php. The manipulation of the argument fromdate/todate leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.