CVE-2025-8156: PHPGurukul User Registration & Login and User Management · SQL Injection
Affects PHPGurukul User Registration & Login and User ManagementSource 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 37% 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 25 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 User Registration & Login and User Management | Affected
| Fixed in– |
AI-suggested
1. Immediate mitigation should include restricting access to the /admin/lastsevendays-reg-users.php endpoint via network controls such as IP whitelisting or VPN-only access to limit exposure. 2. Implement web application firewall (WAF) rules specifically designed to detect and block SQL injection attempts targeting the 'ID' parameter. 3. Conduct a thorough code review and apply input validation and parameterized queries or prepared statements to sanitize all user inputs, especially the 'ID' parameter in the affected script. 4. Monitor application logs for suspicious SQL query patterns or repeated access attempts to the vulnerable endpoint. 5. If possible, isolate the affected application environment to minimize lateral movement risks. 6. Engage with the vendor or community to obtain or develop a security patch and apply it as soon as available. 7. Perform regular vulnerability scanning and penetration testing focused on injection flaws to detect similar issues proactively. 8. Educate development and operations teams on secure coding practices to prevent recurrence of injection vulnerabilities.
Description
A vulnerability was found in PHPGurukul User Registration & Login and User Management 3.3 and classified as critical. Affected by this issue is some unknown functionality of the file /admin/lastsevendays-reg-users.php. The manipulation of the argument ID leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.