CVE-2018-10283

9.8 CRITICAL

📋 TL;DR

This vulnerability allows attackers to execute arbitrary SQL commands through the id parameter in CliqueMania's patch/remote.php file during a recomendar action. It affects CliqueMania loja virtual e-commerce software users. Attackers can potentially access, modify, or delete database content.

💻 Affected Systems

Products:
  • CliqueMania loja virtual
Versions: Version 14
Operating Systems: Any OS running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Affects installations with the vulnerable patch/remote.php file accessible.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including sensitive customer data (PII, payment info), administrative credential theft, and potential remote code execution leading to full system takeover.

🟠

Likely Case

Database information disclosure, data manipulation, and potential administrative access to the e-commerce platform.

🟢

If Mitigated

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

🌐 Internet-Facing: HIGH - The vulnerable endpoint is typically exposed to the internet in e-commerce deployments.
🏢 Internal Only: MEDIUM - If deployed internally only, risk is reduced but still significant for internal data.

🎯 Exploit Status

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

SQL injection via GET/POST parameter requires minimal technical skill to exploit.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: Not available

Restart Required: No

Instructions:

1. Check vendor website for updates. 2. If no patch, implement workarounds. 3. Consider migrating to supported software.

🔧 Temporary Workarounds

Input Validation Filter

all

Add input validation to sanitize the id parameter before processing.

// In patch/remote.php, add: $id = filter_var($_GET['id'], FILTER_VALIDATE_INT); if (!$id) { die('Invalid input'); }

Web Application Firewall Rule

linux

Block SQL injection patterns targeting the vulnerable endpoint.

# ModSecurity rule: SecRule ARGS:id "@detectSQLi" "id:1001,phase:2,deny,status:403,msg:'SQLi attempt detected'"

🧯 If You Can't Patch

  • Implement network segmentation to restrict access to the vulnerable endpoint
  • Deploy a web application firewall (WAF) with SQL injection protection rules

🔍 How to Verify

Check if Vulnerable:

Test the endpoint with SQL injection payloads: http://target/patch/remote.php?action=recomendar&id=1' OR '1'='1

Check Version:

Check software version in admin panel or readme files; no standard command available.

Verify Fix Applied:

Retest with SQL injection payloads; successful fix should return error or no database interaction.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL errors in web server logs
  • Multiple requests to patch/remote.php with suspicious id parameters

Network Indicators:

  • HTTP requests containing SQL keywords (UNION, SELECT, etc.) in id parameter

SIEM Query:

source="web_logs" AND uri="/patch/remote.php" AND (query="*id=*'*" OR query="*id=*%27*")

🔗 References

📤 Share & Export