CVE-2024-13078

6.3 MEDIUM

📋 TL;DR

This critical SQL injection vulnerability in PHPGurukul Land Record System 1.0 allows remote attackers to execute arbitrary SQL commands via the 'searchdata' parameter in /index.php. Attackers can potentially access, modify, or delete database records. All users running the vulnerable version are affected.

💻 Affected Systems

Products:
  • PHPGurukul Land Record System
Versions: 1.0
Operating Systems: Any OS running PHP and MySQL
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the default installation; requires PHP and MySQL backend.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data manipulation, or deletion; potential for authentication bypass and remote code execution if database permissions allow.

🟠

Likely Case

Unauthorized data access and extraction of sensitive land record information; potential for data manipulation or deletion.

🟢

If Mitigated

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

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit details are publicly available; SQL injection via searchdata parameter is straightforward.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://phpgurukul.com/

Restart Required: No

Instructions:

No official patch available. Consider implementing input validation and parameterized queries manually.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement server-side validation and sanitization of the searchdata parameter

Modify /index.php to validate and sanitize searchdata input using PHP functions like mysqli_real_escape_string() or prepared statements

Web Application Firewall (WAF)

all

Deploy WAF rules to block SQL injection attempts

Configure WAF to detect and block SQL injection patterns in searchdata parameter

🧯 If You Can't Patch

  • Implement network segmentation to isolate the vulnerable system
  • Restrict database user permissions to minimum required access

🔍 How to Verify

Check if Vulnerable:

Test /index.php with SQL injection payloads in searchdata parameter (e.g., searchdata=' OR '1'='1)

Check Version:

Check system documentation or configuration files for version information

Verify Fix Applied:

Verify that SQL injection attempts no longer succeed and return proper error handling

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts or unusual search patterns in application logs

Network Indicators:

  • HTTP requests to /index.php with SQL keywords in searchdata parameter

SIEM Query:

source="web_logs" AND uri="/index.php" AND (searchdata CONTAINS "UNION" OR searchdata CONTAINS "SELECT" OR searchdata CONTAINS "OR '1'='1")

🔗 References

📤 Share & Export