CVE-2024-10844

7.3 HIGH

📋 TL;DR

This critical SQL injection vulnerability in Bookstore Management System 1.0 allows attackers to execute arbitrary SQL commands through the search.php file's 's' parameter. Remote attackers can potentially access, modify, or delete database contents. All users running version 1.0 without patches are affected.

💻 Affected Systems

Products:
  • 1000 Projects Bookstore Management System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the search.php file specifically; any installation with this file accessible is vulnerable

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data destruction, authentication bypass, and potential server takeover via SQL injection to RCE chain

🟠

Likely Case

Database information disclosure, data manipulation, and potential privilege escalation

🟢

If Mitigated

Limited impact with proper input validation, parameterized queries, and WAF protection

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Public exploit available on GitHub; simple SQL injection via GET/POST parameter manipulation

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None known

Restart Required: No

Instructions:

1. Check vendor website for updates 2. Apply any available patches 3. Replace vulnerable search.php with secure version if provided

🔧 Temporary Workarounds

Input Validation Filter

all

Add input validation to sanitize the 's' parameter in search.php

Modify search.php to include: $search_term = mysqli_real_escape_string($connection, $_GET['s']);

WAF Rule Implementation

all

Deploy web application firewall rules to block SQL injection patterns

Add WAF rule: Detect and block SQL injection patterns in search.php parameters

🧯 If You Can't Patch

  • Disable or restrict access to search.php file
  • Implement network segmentation and restrict database access from web server

🔍 How to Verify

Check if Vulnerable:

Test search.php with SQL injection payloads like: search.php?s=1' OR '1'='1

Check Version:

Check system documentation or admin panel for version information

Verify Fix Applied:

Test with same payloads; should return error or no database interaction

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed search attempts with special characters
  • Long parameter values in web server logs

Network Indicators:

  • SQL keywords in HTTP GET/POST parameters
  • Unusual database connection patterns from web server

SIEM Query:

source="web_logs" AND (uri="*search.php*" AND (param="*UNION*" OR param="*SELECT*" OR param="*OR '1'='1*"))

🔗 References

📤 Share & Export