CVE-2021-44868

9.8 CRITICAL

📋 TL;DR

CVE-2021-44868 is a SQL injection vulnerability in ming-soft MCMS v5.1 that allows attackers to execute arbitrary SQL commands through the /ms/cms/content/list.do endpoint. This affects all systems running the vulnerable version of MCMS content management software. Attackers can potentially read, modify, or delete database content.

💻 Affected Systems

Products:
  • ming-soft MCMS
Versions: v5.1
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in the default installation of MCMS v5.1.

📦 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

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

🟢

If Mitigated

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

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

SQL injection vulnerabilities in web applications are commonly exploited with automated tools.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: v5.2 or later

Vendor Advisory: https://github.com/ming-soft/MCMS/issues/58

Restart Required: Yes

Instructions:

1. Backup your current installation and database. 2. Download and install MCMS v5.2 or later from the official repository. 3. Restart the web application server. 4. Verify the fix by testing the vulnerable endpoint.

🔧 Temporary Workarounds

WAF Rule Implementation

all

Deploy web application firewall rules to block SQL injection patterns targeting the vulnerable endpoint.

# Example ModSecurity rule: SecRule REQUEST_URI "@contains /ms/cms/content/list.do" "id:1001,phase:2,deny,status:403,msg:'Blocking MCMS SQLi attempt'"
# Add SQL injection detection patterns to your WAF

Endpoint Restriction

linux

Restrict access to the vulnerable endpoint using network controls or application configuration.

# Apache: <Location "/ms/cms/content/list.do"> Require ip 192.168.1.0/24 </Location>
# Nginx: location /ms/cms/content/list.do { deny all; }

🧯 If You Can't Patch

  • Implement strict input validation and parameterized queries in the application code
  • Deploy a web application firewall with SQL injection protection rules

🔍 How to Verify

Check if Vulnerable:

Test the /ms/cms/content/list.do endpoint with SQL injection payloads like ' OR '1'='1 and monitor for database errors or unexpected responses.

Check Version:

Check the MCMS version in the application's admin panel or configuration files.

Verify Fix Applied:

After patching, test the same endpoint with SQL injection payloads and verify they are properly sanitized or rejected.

📡 Detection & Monitoring

Log Indicators:

  • SQL syntax errors in application logs
  • Unusual database queries from the web application
  • Multiple failed login attempts or parameter manipulation

Network Indicators:

  • HTTP requests to /ms/cms/content/list.do with SQL keywords (UNION, SELECT, etc.)
  • Abnormal database connection patterns from the application server

SIEM Query:

source="web_logs" AND uri="/ms/cms/content/list.do" AND (query="*UNION*" OR query="*SELECT*" OR query="*OR*1*" OR status="500")

🔗 References

📤 Share & Export