CVE-2025-6156: PHPGurukul Nipah Virus Testing Management System · SQL Injection
Affects PHPGurukul Nipah Virus Testing Management SystemSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% 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 17 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PHPGurukul Nipah Virus Testing Management System | Affected
| Fixed in– |
AI-suggested
1. Immediate implementation of input validation and parameterized queries in the /bwdates-report-ds.php file to sanitize the 'testtype' parameter and prevent SQL Injection. 2. Restrict network access to the Nipah Virus Testing Management System to trusted internal networks or VPNs, minimizing exposure to the internet. 3. Conduct thorough code reviews and penetration testing focused on SQL Injection and other injection flaws within the application. 4. Implement Web Application Firewalls (WAFs) with custom rules to detect and block SQL Injection attempts targeting the 'testtype' parameter. 5. Monitor application logs for unusual or malformed SQL queries indicative of exploitation attempts. 6. Segregate the database and application servers with strict access controls to limit the impact of a potential breach. 7. Develop and apply patches promptly once available from the vendor or consider migrating to alternative solutions if patching is delayed. 8. Educate IT and security teams on the specific risks associated with this vulnerability and ensure incident response plans include scenarios involving SQL Injection in critical health systems.
Description
A vulnerability was found in PHPGurukul Nipah Virus Testing Management System 1.0. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /bwdates-report-ds.php. The manipulation of the argument testtype leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.