CVE-2025-1906

4.7 MEDIUM

📋 TL;DR

This critical SQL injection vulnerability in PHPGurukul Restaurant Table Booking System 1.0 allows attackers to manipulate database queries through the mobilenumber parameter in /admin/profile.php. Attackers can potentially access, modify, or delete sensitive data including user credentials and booking information. All users running version 1.0 are affected.

💻 Affected Systems

Products:
  • PHPGurukul Restaurant Table Booking System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Requires admin access to reach /admin/profile.php, but SQL injection can be exploited by authenticated attackers.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, account takeover, and potential remote code execution if database permissions allow.

🟠

Likely Case

Unauthorized access to sensitive booking data, user information, and potential privilege escalation within the application.

🟢

If Mitigated

Limited impact if proper input validation and parameterized queries are implemented, restricting attackers to read-only data access.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit details are publicly available on GitHub, making this easily exploitable by attackers with basic SQL injection knowledge.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://phpgurukul.com/

Restart Required: No

Instructions:

No official patch available. Consider migrating to alternative software or implementing custom fixes with parameterized queries.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement strict input validation for mobilenumber parameter and all user inputs in profile.php

Modify /admin/profile.php to use prepared statements with parameterized queries

Web Application Firewall Rules

all

Deploy WAF rules to block SQL injection patterns targeting mobilenumber parameter

Add WAF rule: Detect and block SQL injection attempts in POST parameters

🧯 If You Can't Patch

  • Isolate the system behind a reverse proxy with strict input filtering
  • Implement network segmentation to limit database access from the web server

🔍 How to Verify

Check if Vulnerable:

Test the mobilenumber parameter in /admin/profile.php with SQL injection payloads like ' OR '1'='1

Check Version:

Check system documentation or admin panel for version information

Verify Fix Applied:

Verify that parameterized queries are implemented and SQL injection attempts return errors or are blocked

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL errors in application logs
  • Multiple failed login attempts followed by profile.php access
  • Suspicious mobilenumber parameter values containing SQL keywords

Network Indicators:

  • Unusual database queries originating from web server
  • Patterns of SQL injection attempts in HTTP requests

SIEM Query:

source="web_logs" AND (uri="/admin/profile.php" AND (param="mobilenumber" AND value MATCH "'.*[Ss][Ee][Ll][Ee][Cc][Tt].*'"))

🔗 References

📤 Share & Export