CVE-2025-8157: 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 25 Oct 2026, 19:02 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: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-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PHPGurukul User Registration & Login and User Management | Affected
| Fixed in– |
AI-suggested
Given the absence of an official patch, European organizations should immediately audit their use of PHPGurukul User Registration & Login and User Management version 3.3 and consider the following mitigations: 1) Restrict access to the /admin/lastthirtyays-reg-users.php endpoint using network-level controls such as IP whitelisting or VPN access to limit exposure to trusted administrators only. 2) Implement Web Application Firewall (WAF) rules specifically designed to detect and block SQL injection attempts targeting the 'ID' parameter, using signature-based and anomaly detection techniques. 3) Conduct thorough input validation and sanitization on all user-supplied parameters, especially the 'ID' argument, to prevent injection of malicious SQL code. 4) Monitor application logs and database queries for unusual activity indicative of exploitation attempts. 5) Plan and prioritize upgrading or replacing the vulnerable software component with a patched or more secure alternative once available. 6) Educate administrators and developers about the risks of SQL injection and secure coding practices to prevent similar vulnerabilities in the future.
Description
A vulnerability was found in PHPGurukul User Registration & Login and User Management 3.3. It has been classified as critical. This affects an unknown part of the file /admin/lastthirtyays-reg-users.php. The manipulation of the argument ID leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.