CVE-2025-5652

6.3 MEDIUM

📋 TL;DR

This critical vulnerability in PHPGurukul Complaint Management System 2.0 allows remote attackers to execute SQL injection attacks via the fromdate/todate parameters in the /admin/between-date-complaintreport.php file. This can lead to unauthorized database access, data theft, or system compromise. Organizations using this specific software version are affected.

💻 Affected Systems

Products:
  • PHPGurukul Complaint Management System
Versions: 2.0
Operating Systems: All platforms running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Requires the /admin/between-date-complaintreport.php file to be accessible, which is part of the default installation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data exfiltration, privilege escalation, or full system takeover via SQL injection.

🟠

Likely Case

Unauthorized access to sensitive complaint data, user information, or administrative credentials stored in the database.

🟢

If Mitigated

Limited impact with proper input validation, WAF protection, and database permission restrictions in place.

🌐 Internet-Facing: HIGH - Attack can be launched remotely without authentication, making internet-facing instances particularly vulnerable.
🏢 Internal Only: MEDIUM - Internal attackers or compromised internal systems could exploit this vulnerability.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploit details are publicly available on GitHub, making this easily exploitable by attackers with basic SQL injection knowledge.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://phpgurukul.com/

Restart Required: No

Instructions:

No official patch available. Check vendor website for updates or consider alternative solutions.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement strict input validation and parameterized queries for the fromdate and todate parameters.

Modify /admin/between-date-complaintreport.php to use prepared statements with bound parameters

Access Restriction

all

Restrict access to the vulnerable file using web server configuration or authentication.

Add authentication requirement or IP restriction to /admin/between-date-complaintreport.php

🧯 If You Can't Patch

  • Implement a Web Application Firewall (WAF) with SQL injection protection rules
  • Isolate the system from internet access and restrict internal network access

🔍 How to Verify

Check if Vulnerable:

Test the /admin/between-date-complaintreport.php endpoint with SQL injection payloads in fromdate/todate parameters.

Check Version:

Check the software version in the application interface or configuration files.

Verify Fix Applied:

Verify that SQL injection attempts no longer succeed and that input validation is properly implemented.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts from single IP
  • Access to /admin/between-date-complaintreport.php with suspicious parameters

Network Indicators:

  • SQL injection patterns in HTTP requests to the vulnerable endpoint
  • Unusual database connection patterns

SIEM Query:

source="web_logs" AND uri="/admin/between-date-complaintreport.php" AND (query CONTAINS "UNION" OR query CONTAINS "SELECT" OR query CONTAINS "OR 1=1")

🔗 References

📤 Share & Export