CVE-2026-3790

6.3 MEDIUM

📋 TL;DR

This SQL injection vulnerability in SourceCodester Sales and Inventory System 1.0 allows remote attackers to execute arbitrary SQL commands via the stock_name1 parameter in check_supplier_details.php. Organizations using this specific version of the inventory system are affected, potentially exposing database contents including sensitive business data.

💻 Affected Systems

Products:
  • SourceCodester Sales and Inventory System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects systems with the vulnerable check_supplier_details.php file accessible via web interface.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, data manipulation, or system takeover via SQL injection to execute arbitrary commands.

🟠

Likely Case

Unauthorized access to sensitive inventory and supplier data, potential data exfiltration, and database integrity compromise.

🟢

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

Public proof-of-concept available on GitHub demonstrates exploitation via POST request manipulation.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

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

Restart Required: No

Instructions:

No official patch available. Consider implementing input validation and parameterized queries as workaround.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement server-side validation to sanitize stock_name1 parameter before processing.

Modify check_supplier_details.php to add: $stock_name1 = mysqli_real_escape_string($conn, $_POST['stock_name1']);

Web Application Firewall (WAF) Rules

all

Deploy WAF rules to block SQL injection patterns in POST parameters.

Add WAF rule: Detect and block requests containing SQL keywords like UNION, SELECT, INSERT in POST body

🧯 If You Can't Patch

  • Restrict network access to the application using firewall rules to only trusted IP addresses.
  • Implement database user with minimal privileges (read-only if possible) for the application connection.

🔍 How to Verify

Check if Vulnerable:

Test by sending POST request to check_supplier_details.php with SQL injection payload in stock_name1 parameter and observe database errors or unexpected responses.

Check Version:

Check application version in admin panel or review source code comments for version information.

Verify Fix Applied:

Attempt same SQL injection payload after implementing fixes; should receive sanitized response or error without database exposure.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL error messages in web server logs
  • Multiple failed login attempts or parameter manipulation in access logs

Network Indicators:

  • POST requests to check_supplier_details.php containing SQL keywords in parameters
  • Unusual database query patterns from web server IP

SIEM Query:

source="web_logs" AND uri="*check_supplier_details.php*" AND (param="*stock_name1*" AND value="*UNION*" OR value="*SELECT*" OR value="*INSERT*")

🔗 References

📤 Share & Export