CVE-2024-13014

6.3 MEDIUM

📋 TL;DR

This critical SQL injection vulnerability in PHPGurukul Maid Hiring Management System 1.0 allows attackers to execute arbitrary SQL commands via the searchdata parameter in /admin/search-maid.php. Attackers can remotely exploit this to access, modify, or delete database content. Organizations using this specific version of the software are affected.

💻 Affected Systems

Products:
  • PHPGurukul Maid Hiring Management System
Versions: 1.0
Operating Systems: All platforms running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Requires PHP environment with database backend. The /admin/search-maid.php file must be accessible.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data destruction, privilege escalation to admin access, and potential server takeover via SQL injection to RCE chaining.

🟠

Likely Case

Unauthorized access to sensitive maid and client data, potential credential theft from database, and system integrity compromise.

🟢

If Mitigated

Limited impact with proper input validation, parameterized queries, and database permission restrictions in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit requires admin access to reach the vulnerable endpoint. SQL injection is straightforward once authenticated.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://phpgurukul.com/

Restart Required: No

Instructions:

No official patch available. Implement input validation and parameterized queries in /admin/search-maid.php. Replace raw SQL queries with prepared statements.

🔧 Temporary Workarounds

Input Validation Filter

all

Add server-side validation to sanitize searchdata parameter before processing

Add validation in PHP: if(!preg_match('/^[a-zA-Z0-9\s]+$/', $_POST['searchdata'])) { die('Invalid input'); }

WAF Rule Implementation

all

Deploy web application firewall rules to block SQL injection patterns

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

🧯 If You Can't Patch

  • Restrict access to /admin/search-maid.php using IP whitelisting or additional authentication
  • Implement database user with minimal permissions (read-only if possible) for the application

🔍 How to Verify

Check if Vulnerable:

Test the search functionality with SQL injection payloads like ' OR '1'='1 in the searchdata parameter

Check Version:

Check system documentation or about page for version information

Verify Fix Applied:

Attempt SQL injection tests and verify they are blocked or sanitized without affecting legitimate searches

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts followed by search requests
  • Requests to /admin/search-maid.php with special characters in parameters

Network Indicators:

  • HTTP POST requests to /admin/search-maid.php containing SQL keywords (UNION, SELECT, etc.)

SIEM Query:

source="web_logs" AND uri_path="/admin/search-maid.php" AND (request_body LIKE "%UNION%" OR request_body LIKE "%SELECT%" OR request_body LIKE "%OR%1%1%")

🔗 References

📤 Share & Export