Skip to main content
VulnerabilityPublished

CVE-2025-5659: PHPGurukul Complaint Management System · SQL Injection

Affects PHPGurukul Complaint Management SystemSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
PHPGurukul Complaint Management SystemAffected
  • =2.0
Fixed in–

AI-suggested

  1. Immediate mitigation should include implementing input validation and parameterized queries (prepared statements) for the 'pincode' parameter to prevent SQL injection.
  2. Conduct a thorough code review of the /user/profile.php file and other input points to identify and remediate similar injection flaws.
  3. Restrict direct external access to the complaint management system where possible, using network segmentation and firewall rules.
  4. Monitor web application logs for suspicious input patterns targeting the 'pincode' parameter.
  5. Apply web application firewalls (WAFs) with custom rules to detect and block SQL injection attempts.
  6. Engage with the vendor or community to obtain or develop official patches or updates.
  7. Educate developers and administrators on secure coding practices and regular vulnerability assessments.
  8. Implement strict access controls and database permissions to limit the impact of a potential injection attack.
  9. 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.

References

Community reviews

Loading reviews…