CVE-2025-5659: PHPGurukul Complaint Management System · SQL Injection
Affects PHPGurukul Complaint Management SystemSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% 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 5 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 |
|---|---|---|
| PHPGurukul Complaint Management System | Affected
| Fixed in– |
AI-suggested
- Immediate mitigation should include implementing input validation and parameterized queries (prepared statements) for the 'pincode' parameter to prevent SQL injection.
- Conduct a thorough code review of the /user/profile.php file and other input points to identify and remediate similar injection flaws.
- Restrict direct external access to the complaint management system where possible, using network segmentation and firewall rules.
- Monitor web application logs for suspicious input patterns targeting the 'pincode' parameter.
- Apply web application firewalls (WAFs) with custom rules to detect and block SQL injection attempts.
- Engage with the vendor or community to obtain or develop official patches or updates.
- Educate developers and administrators on secure coding practices and regular vulnerability assessments.
- Implement strict access controls and database permissions to limit the impact of a potential injection attack.
- Backup complaint data regularly to enable recovery in case of data tampering or loss.
Description
A vulnerability classified as critical was found in PHPGurukul Complaint Management System 2.0. Affected by this vulnerability is an unknown functionality of the file /user/profile.php. The manipulation of the argument pincode leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.