CVE-2025-4924

7.3 HIGH

📋 TL;DR

A critical SQL injection vulnerability exists in SourceCodester Client Database Management System 1.0 through the /user_void_transaction.php file's order_id parameter. This allows remote attackers to execute arbitrary SQL commands on the database. All users running the vulnerable version are affected.

💻 Affected Systems

Products:
  • SourceCodester Client Database Management System
Versions: 1.0
Operating Systems: Any OS running PHP/MySQL web server
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all installations of version 1.0 with the vulnerable file present.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

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

🟠

Likely Case

Unauthorized access to sensitive client data, database manipulation, or potential privilege escalation.

🟢

If Mitigated

Limited impact with proper input validation and database permissions, though SQL injection attempts would still be logged.

🌐 Internet-Facing: HIGH - Attack can be launched remotely without authentication.
🏢 Internal Only: MEDIUM - Internal attackers could exploit, but external threat is higher.

🎯 Exploit Status

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

Exploit details are publicly available on GitHub, making this easily exploitable.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://www.sourcecodester.com/

Restart Required: No

Instructions:

No official patch available. Check vendor website for updates or apply workarounds.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Add proper input validation and parameterized queries to /user_void_transaction.php

Edit PHP file to use prepared statements: $stmt = $conn->prepare('SELECT * FROM table WHERE order_id = ?'); $stmt->bind_param('s', $order_id);

Web Application Firewall (WAF)

all

Deploy WAF rules to block SQL injection patterns

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

🧯 If You Can't Patch

  • Restrict network access to the application using firewall rules
  • Implement database user with minimal required permissions

🔍 How to Verify

Check if Vulnerable:

Check if /user_void_transaction.php exists and contains unsanitized order_id parameter usage

Check Version:

Check application version in admin panel or readme files

Verify Fix Applied:

Test with SQL injection payloads like ' OR '1'='1 in order_id parameter

📡 Detection & Monitoring

Log Indicators:

  • SQL syntax errors in web server logs
  • Unusual database queries from web application

Network Indicators:

  • HTTP requests to /user_void_transaction.php with SQL keywords in parameters

SIEM Query:

source="web.log" AND uri="/user_void_transaction.php" AND (order_id="*'*" OR order_id="*SELECT*" OR order_id="*UNION*")

🔗 References

📤 Share & Export