CVE-2024-7306

6.3 MEDIUM

📋 TL;DR

This is a critical SQL injection vulnerability in SourceCodester Establishment Billing Management System 1.0. Attackers can remotely exploit the /manage_block.php file by manipulating the 'id' parameter to execute arbitrary SQL commands. All users running this specific version of the billing management system are affected.

💻 Affected Systems

Products:
  • SourceCodester Establishment Billing Management System
Versions: 1.0
Operating Systems: Any OS running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects version 1.0. Requires PHP environment with database connectivity.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, data manipulation, authentication bypass, or full system takeover via SQL injection to RCE chaining.

🟠

Likely Case

Database information disclosure, data manipulation, and potential privilege escalation within the application.

🟢

If Mitigated

Limited impact with proper input validation and WAF rules blocking SQL injection patterns.

🌐 Internet-Facing: HIGH - The vulnerability is remotely exploitable and a public exploit exists.
🏢 Internal Only: MEDIUM - Internal attackers could exploit this if they have network access to the system.

🎯 Exploit Status

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

Exploit code is publicly available on GitHub Gist. The vulnerability requires no authentication and has simple exploitation vectors.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None found

Restart Required: No

Instructions:

No official patch available. Consider upgrading to a newer version if available, or implement workarounds.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Add proper input validation and parameterized queries to the /manage_block.php file

Modify PHP code to use prepared statements: $stmt = $conn->prepare('SELECT * FROM blocks WHERE id = ?'); $stmt->bind_param('i', $id);

WAF Rule Implementation

all

Deploy web application firewall rules to block SQL injection patterns

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

🧯 If You Can't Patch

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

🔍 How to Verify

Check if Vulnerable:

Test the /manage_block.php endpoint with SQL injection payloads like: /manage_block.php?id=1' OR '1'='1

Check Version:

Check application version in admin panel or readme files

Verify Fix Applied:

Test with the same payloads after implementing fixes - should return error pages or no data leakage

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL error messages in web server logs
  • Multiple requests to /manage_block.php with SQL-like parameters

Network Indicators:

  • HTTP requests containing SQL keywords (UNION, SELECT, etc.) in URL parameters

SIEM Query:

source="web_logs" AND url="/manage_block.php" AND (url="*UNION*" OR url="*SELECT*" OR url="*OR '1'='1*")

🔗 References

📤 Share & Export