CVE-2025-7539

7.3 HIGH

📋 TL;DR

This critical SQL injection vulnerability in code-projects Online Appointment Booking System 1.0 allows remote attackers to execute arbitrary SQL commands via the 'cid' parameter in /getdoctordaybooking.php. This can lead to unauthorized data access, modification, or deletion. All users running version 1.0 without proper input validation are affected.

💻 Affected Systems

Products:
  • code-projects Online Appointment Booking System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all installations of version 1.0. The vulnerability is in the core application code.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including sensitive data exfiltration, authentication bypass, remote code execution, and system takeover

🟠

Likely Case

Unauthorized access to appointment data, patient information, and potential privilege escalation

🟢

If Mitigated

Limited impact with proper input validation and database permissions, potentially only error messages or limited data exposure

🌐 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 via URL parameter requires minimal technical skill.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://code-projects.org/

Restart Required: No

Instructions:

1. Check vendor website for updates 2. If no patch available, implement workarounds 3. Consider migrating to alternative software

🔧 Temporary Workarounds

Input Validation Filter

all

Add server-side validation to sanitize the 'cid' parameter

Add parameter validation in PHP: $cid = filter_var($_GET['cid'], FILTER_VALIDATE_INT); if($cid === false) { die('Invalid input'); }

Web Application Firewall Rule

all

Block SQL injection patterns targeting /getdoctordaybooking.php

ModSecurity rule: SecRule ARGS:cid "@detectSQLi" "id:1001,phase:2,deny,status:403,msg:'SQLi attempt detected'"

🧯 If You Can't Patch

  • Implement network segmentation to isolate the vulnerable system from sensitive data
  • Deploy a web application firewall (WAF) with SQL injection protection rules

🔍 How to Verify

Check if Vulnerable:

Test /getdoctordaybooking.php?cid=1' OR '1'='1 and check for SQL errors or unexpected behavior

Check Version:

Check application files or documentation for version information

Verify Fix Applied:

Test with SQL injection payloads and verify proper error handling or rejection

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL errors in application logs
  • Multiple requests to /getdoctordaybooking.php with special characters in parameters
  • Database queries with UNION, SELECT, or other SQL keywords from web requests

Network Indicators:

  • HTTP requests containing SQL keywords (UNION, SELECT, INSERT) in URL parameters
  • Unusual traffic patterns to the vulnerable endpoint

SIEM Query:

source="web_logs" AND uri_path="/getdoctordaybooking.php" AND (query_string="*UNION*" OR query_string="*SELECT*" OR query_string="*' OR '*" OR query_string="*--*" OR query_string="*;*" OR query_string="*/*")

🔗 References

📤 Share & Export