Skip to main content
VulnerabilityPublished

CVE-2025-5652: 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, 09:15 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

Organizations should immediately audit their use of PHPGurukul Complaint Management System 2.0 and restrict access to the /admin/between-date-complaintreport.php endpoint to trusted administrators only, ideally via network segmentation or VPN access. Input validation and parameter sanitization should be implemented or enhanced to ensure 'fromdate' and 'todate' parameters accept only valid date formats and reject any SQL metacharacters. Employing prepared statements or parameterized queries in the backend code is strongly recommended to prevent injection. Monitoring and logging access to the complaint report functionality can help detect suspicious activity. Until an official patch is released, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting these parameters. Additionally, conduct regular security assessments and penetration tests focusing on this module. Finally, maintain backups of complaint data to enable recovery in case of data corruption or loss.

Description

A vulnerability, which was classified as critical, was found in PHPGurukul Complaint Management System 2.0. Affected is an unknown function of the file /admin/between-date-complaintreport.php. The manipulation of the argument fromdate/todate leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…