CVE-2025-1964

7.3 HIGH

📋 TL;DR

This critical SQL injection vulnerability in Online Hotel Booking 1.0 allows remote attackers to execute arbitrary SQL commands via the 'checkin' parameter in the /booknow.php endpoint. Attackers can potentially access, modify, or delete database content, including sensitive guest information. All systems running the vulnerable software are affected.

💻 Affected Systems

Products:
  • projectworlds Online Hotel Booking
Versions: 1.0
Operating Systems: Any OS running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the /booknow.php endpoint with roomname=Duplex parameter, but other parameters may also be vulnerable

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, data destruction, or full system takeover via SQL injection to RCE chaining

🟠

Likely Case

Unauthorized access to sensitive guest data (personal information, payment details), database manipulation, or denial of service

🟢

If Mitigated

Limited impact with proper input validation, parameterized queries, and network segmentation in place

🌐 Internet-Facing: HIGH - The vulnerability is remotely exploitable via web interface with public exploit available
🏢 Internal Only: MEDIUM - Internal systems still vulnerable but attack surface reduced compared to internet-facing deployments

🎯 Exploit Status

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

Exploit code is publicly available on GitHub, making attacks easy for even low-skilled attackers

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None known

Restart Required: No

Instructions:

No official patch available. Implement workarounds or consider replacing the software.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement strict input validation and parameterized queries for all user inputs

Modify booknow.php to use prepared statements: $stmt = $conn->prepare('SELECT * FROM bookings WHERE checkin = ?'); $stmt->bind_param('s', $checkin);

Web Application Firewall (WAF)

all

Deploy WAF rules to block SQL injection patterns

Add WAF rule: SecRule ARGS:checkin "@detectSQLi" "id:1001,phase:2,deny,status:403"

🧯 If You Can't Patch

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

🔍 How to Verify

Check if Vulnerable:

Test the /booknow.php?roomname=Duplex&checkin= parameter with SQL injection payloads like ' OR '1'='1

Check Version:

Check PHP files for version comments or review software documentation

Verify Fix Applied:

Verify that SQL injection payloads no longer execute and return proper error handling

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts from single IP
  • Suspicious patterns in checkin parameter values

Network Indicators:

  • HTTP requests with SQL keywords in parameters
  • Unusual traffic to /booknow.php endpoint

SIEM Query:

source="web_logs" AND uri="/booknow.php" AND (param="checkin" AND value MATCHES "(?i)(union|select|insert|delete|update|drop|--|' OR)")

🔗 References

📤 Share & Export