CVE-2024-44636

6.5 MEDIUM

📋 TL;DR

This SQL injection vulnerability in PHPGurukul Student Record System 3.20 allows attackers to manipulate database queries through the adminname and aemailid parameters in /admin-profile.php. Attackers could potentially access, modify, or delete sensitive student and administrative data. Organizations using this specific version of the student record system are affected.

💻 Affected Systems

Products:
  • PHPGurukul Student Record System
Versions: Version 3.20
Operating Systems: Any OS running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Requires admin access to reach /admin-profile.php endpoint, but SQL injection occurs after authentication.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, data destruction, or full system takeover through privilege escalation.

🟠

Likely Case

Unauthorized access to sensitive student records, administrative credentials, or personal information stored in the database.

🟢

If Mitigated

Limited impact with proper input validation and database permissions preventing data exfiltration or modification.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Requires authenticated admin access but SQL injection itself 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 available, download and replace current installation. 3. Validate all user inputs in admin-profile.php. 4. Use prepared statements or parameterized queries.

🔧 Temporary Workarounds

Input Validation Filter

all

Add server-side validation for adminname and aemailid parameters

Edit /admin-profile.php to add: $adminname = filter_var($_POST['adminname'], FILTER_SANITIZE_STRING);
$aemailid = filter_var($_POST['aemailid'], FILTER_SANITIZE_EMAIL);

WAF Rule Implementation

linux

Add web application firewall rules to block SQL injection patterns

ModSecurity rule: SecRule ARGS "@detectSQLi" "id:1001,phase:2,deny,status:403"

🧯 If You Can't Patch

  • Implement strict input validation and parameterized queries in the affected PHP file.
  • Restrict database user permissions to read-only for the application account.

🔍 How to Verify

Check if Vulnerable:

Test /admin-profile.php endpoint with SQL injection payloads in adminname and aemailid parameters after authentication.

Check Version:

Check system documentation or admin panel for version information; typically displayed in footer or about page.

Verify Fix Applied:

Attempt SQL injection tests after implementing fixes; successful queries should be blocked or sanitized.

📡 Detection & Monitoring

Log Indicators:

  • Unusual database query patterns in PHP error logs
  • Multiple failed login attempts followed by admin-profile.php access
  • SQL syntax errors in web server logs

Network Indicators:

  • HTTP POST requests to /admin-profile.php with SQL keywords in parameters
  • Unusual database connection patterns from web server

SIEM Query:

source="web_logs" AND uri="/admin-profile.php" AND (param="adminname" OR param="aemailid") AND (query="UNION" OR query="SELECT" OR query="INSERT" OR query="DELETE")

🔗 References

📤 Share & Export