CVE-2024-44633

6.5 MEDIUM

📋 TL;DR

This vulnerability allows attackers to execute arbitrary SQL commands via the currentpassword parameter in change-password.php. It affects PHPGurukul Student Record System 3.20 installations, potentially compromising student data and system integrity.

💻 Affected Systems

Products:
  • PHPGurukul Student Record System
Versions: Version 3.20
Operating Systems: Any OS running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Requires PHP environment with database backend (typically MySQL).

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, authentication bypass, privilege escalation, and potential remote code execution.

🟠

Likely Case

Unauthorized access to student records, grade manipulation, and extraction of sensitive personal information.

🟢

If Mitigated

Limited impact with proper input validation and database permissions restricting damage to non-critical data.

🌐 Internet-Facing: HIGH - Web application accessible from internet with SQL injection vulnerability.
🏢 Internal Only: MEDIUM - Internal users could exploit but requires access to the application.

🎯 Exploit Status

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

Exploitation requires authentication to access change-password.php, but SQL injection is straightforward once authenticated.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://phpgurukul.com/student-record-system-php

Restart Required: No

Instructions:

1. Check vendor website for updated version. 2. If no patch, implement parameterized queries in change-password.php. 3. Validate and sanitize currentpassword input.

🔧 Temporary Workarounds

Input Validation Filter

all

Add server-side validation to reject malicious SQL characters in currentpassword parameter.

Add PHP validation: if(preg_match('/[\'\"\;\-\-\/\*\=\s]/', $_POST['currentpassword'])) { die('Invalid input'); }

Web Application Firewall Rule

all

Block SQL injection patterns targeting change-password.php endpoint.

WAF rule: Block requests to /change-password.php containing SQL keywords in POST parameters.

🧯 If You Can't Patch

  • Implement network segmentation to restrict access to the application.
  • Enable detailed logging of all change-password.php requests and monitor for SQL patterns.

🔍 How to Verify

Check if Vulnerable:

Test change-password.php with SQL injection payloads in currentpassword parameter (e.g., ' OR '1'='1).

Check Version:

Check application files or admin panel for version 3.20 indication.

Verify Fix Applied:

Verify parameterized queries are implemented and test with same SQL injection payloads expecting failure.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL errors in application logs
  • Multiple failed password change attempts with special characters

Network Indicators:

  • HTTP POST requests to change-password.php containing SQL keywords like UNION, SELECT, OR

SIEM Query:

source="web_logs" AND uri="/change-password.php" AND (request_body LIKE "%OR%" OR request_body LIKE "%UNION%" OR request_body LIKE "%SELECT%")

🔗 References

📤 Share & Export