CVE-2025-1894

7.3 HIGH

📋 TL;DR

This critical SQL injection vulnerability in PHPGurukul Restaurant Table Booking System 1.0 allows attackers to execute arbitrary SQL commands via the searchdata parameter in /search-result.php. Attackers can remotely exploit this to access, modify, or delete database content. All systems running the vulnerable version are affected.

💻 Affected Systems

Products:
  • PHPGurukul Restaurant Table Booking System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in the default installation. Any system with the vulnerable file accessible is at risk.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data destruction, authentication bypass, and potential remote code execution via database functions.

🟠

Likely Case

Unauthorized data access, extraction of sensitive information (customer data, credentials), and potential privilege escalation.

🟢

If Mitigated

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

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit details are publicly available on GitHub. SQL injection vulnerabilities are commonly weaponized with automated tools.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://phpgurukul.com/

Restart Required: No

Instructions:

No official patch available. Consider implementing workarounds or replacing the software.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Add server-side validation to sanitize searchdata parameter before processing

Edit /search-result.php to add: $searchdata = mysqli_real_escape_string($conn, $_POST['searchdata']);

Web Application Firewall (WAF)

all

Deploy WAF rules to block SQL injection patterns in searchdata parameter

🧯 If You Can't Patch

  • Restrict access to /search-result.php using IP whitelisting or authentication
  • Disable the search functionality entirely if not critical to operations

🔍 How to Verify

Check if Vulnerable:

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

Check Version:

Check system documentation or contact vendor for version information

Verify Fix Applied:

Test with same payloads after implementing fixes - should return no data or error messages

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL error messages in application logs
  • Multiple failed search attempts with special characters
  • Unexpected database queries from web server

Network Indicators:

  • HTTP POST requests to /search-result.php containing SQL keywords (UNION, SELECT, INSERT)
  • Abnormal database connection patterns from web server

SIEM Query:

source="web_logs" AND uri="/search-result.php" AND (searchdata CONTAINS "UNION" OR searchdata CONTAINS "SELECT" OR searchdata CONTAINS "' OR '")

🔗 References

📤 Share & Export