CVE-2018-19925

9.8 CRITICAL

📋 TL;DR

This vulnerability allows attackers to execute arbitrary SQL commands through the member/member_order.php type parameter in Sales & Company Management System (SCMS). It affects all SCMS installations up to version 2018-06-06. Attackers can potentially access, modify, or delete database content.

💻 Affected Systems

Products:
  • Sales & Company Management System (SCMS)
Versions: All versions through 2018-06-06
Operating Systems: Any OS running PHP/MySQL web server
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all installations with the vulnerable member/member_order.php file.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

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

🟠

Likely Case

Unauthorized access to sensitive business data, customer information, and potential privilege escalation within the application.

🟢

If Mitigated

Limited impact with proper input validation and parameterized queries preventing SQL injection.

🌐 Internet-Facing: HIGH - Directly exploitable via web interface without authentication.
🏢 Internal Only: MEDIUM - Still exploitable by internal users or compromised accounts.

🎯 Exploit Status

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

Simple SQL injection via GET/POST parameters with public proof-of-concept available.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: No official vendor advisory found

Restart Required: No

Instructions:

1. Check if vendor released updated version after 2018-06-06. 2. Apply manual code fix by implementing parameterized queries. 3. Replace vulnerable member/member_order.php with secure version.

🔧 Temporary Workarounds

Input Validation Filter

all

Add server-side validation to reject malicious SQL characters in type parameter

# In PHP: filter_input(INPUT_GET, 'type', FILTER_SANITIZE_STRING);

WAF Rule

all

Implement web application firewall rules to block SQL injection patterns

# ModSecurity rule: SecRule ARGS:type "@detectSQLi" "id:1001,phase:2,deny"

🧯 If You Can't Patch

  • Block external access to SCMS application at network perimeter
  • Implement strict database user permissions with read-only access where possible

🔍 How to Verify

Check if Vulnerable:

Test member/member_order.php with SQL injection payloads like: ' OR '1'='1

Check Version:

Check SCMS version in admin panel or config files

Verify Fix Applied:

Verify parameterized queries are used and SQL injection attempts return errors without executing

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts after SQL errors
  • Requests to member/member_order.php with SQL keywords

Network Indicators:

  • HTTP requests containing SQL syntax in parameters
  • Unusual database connection patterns from web server

SIEM Query:

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

🔗 References

📤 Share & Export