CVE-2024-10331

6.3 MEDIUM

📋 TL;DR

This critical SQL injection vulnerability in PHPGurukul Vehicle Record System 1.0 allows attackers to execute arbitrary SQL commands via the searchinputdata parameter in /admin/search-vehicle.php. Remote attackers can potentially access, modify, or delete database content. All users running the vulnerable version are affected.

💻 Affected Systems

Products:
  • PHPGurukul Vehicle Record System
Versions: 1.0
Operating Systems: All platforms running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Requires admin panel access (/admin/search-vehicle.php) but SQL injection can bypass authentication if chained with other vulnerabilities.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data destruction, authentication bypass, and potential server takeover via SQL injection to RCE chaining.

🟠

Likely Case

Unauthorized access to vehicle records, personal data exposure, and database manipulation affecting system integrity.

🟢

If Mitigated

Limited impact with proper input validation, parameterized queries, and network segmentation preventing database access.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit requires admin panel access but SQL injection payloads are simple and well-documented. Public disclosure increases weaponization risk.

🛠️ 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. Consider migrating to alternative software if no fix is provided.

🔧 Temporary Workarounds

Input Validation Filter

all

Add server-side input validation to reject malicious SQL characters in searchinputdata parameter

// PHP example: if(preg_match('/[\'"\;\-\-]/', $_POST['searchinputdata'])) { die('Invalid input'); }

WAF Rule Implementation

all

Deploy web application firewall rules to block SQL injection patterns

# ModSecurity example: SecRule ARGS:searchinputdata "@detectSQLi" "id:1001,phase:2,deny"

🧯 If You Can't Patch

  • Disable or restrict access to /admin/search-vehicle.php via .htaccess or web server configuration
  • Implement network segmentation to isolate the database server and restrict outbound connections

🔍 How to Verify

Check if Vulnerable:

Test searchinputdata parameter with SQL injection payloads like ' OR '1'='1 and monitor database errors

Check Version:

Check system documentation or admin panel footer for version information

Verify Fix Applied:

Test with same payloads after implementing fixes - should return validation errors or no database errors

📡 Detection & Monitoring

Log Indicators:

  • SQL syntax errors in web server logs
  • Unusual database query patterns from web server IP
  • Multiple failed login attempts followed by search queries

Network Indicators:

  • HTTP POST requests to /admin/search-vehicle.php with SQL keywords in parameters
  • Unusual database port connections from web server

SIEM Query:

source="web_logs" AND uri="/admin/search-vehicle.php" AND (searchinputdata="*'*" OR searchinputdata="*--*" OR searchinputdata="*OR*" OR searchinputdata="*UNION*")

🔗 References

📤 Share & Export