CVE-2024-10991

7.3 HIGH

📋 TL;DR

This critical SQL injection vulnerability in Codezips Hospital Appointment System 1.0 allows remote attackers to execute arbitrary SQL commands via the ID parameter in /editBranchResult.php. This could lead to unauthorized data access, modification, or deletion. All systems running the vulnerable version are affected.

💻 Affected Systems

Products:
  • Codezips Hospital Appointment System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in the default installation. No special configuration is required for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including patient medical records, appointment data, and administrative credentials leading to data theft, system takeover, or ransomware deployment.

🟠

Likely Case

Unauthorized access to sensitive patient and hospital data, potential data manipulation or deletion, and possible 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 vulnerabilities are commonly weaponized due to their simplicity and impact.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None known

Restart Required: No

Instructions:

No official patch available. Consider migrating to a supported alternative or implementing workarounds.

🔧 Temporary Workarounds

Input Validation Filter

all

Add server-side validation to sanitize the ID parameter before processing

Modify /editBranchResult.php to validate ID parameter using prepared statements or parameterized queries

Web Application Firewall

all

Deploy WAF rules to block SQL injection attempts

Add WAF rule: deny requests with SQL keywords in ID parameter

🧯 If You Can't Patch

  • Isolate the system behind a firewall with strict access controls
  • Implement network segmentation to limit database access from the application server

🔍 How to Verify

Check if Vulnerable:

Test the /editBranchResult.php endpoint with SQL injection payloads in the ID parameter (e.g., ID=1' OR '1'='1)

Check Version:

Check system documentation or admin panel for version information

Verify Fix Applied:

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

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL error messages in application logs
  • Multiple failed login attempts following SQL injection patterns
  • Unexpected database queries from application user

Network Indicators:

  • HTTP requests to /editBranchResult.php with SQL keywords in parameters
  • Unusual database traffic patterns from application server

SIEM Query:

source="web_logs" AND uri="/editBranchResult.php" AND (param="ID" AND value MATCHES "(?i)(union|select|insert|update|delete|drop|or|and|'|--|#)")

🔗 References

📤 Share & Export