CVE-2023-46800

9.8 CRITICAL

📋 TL;DR

Online Matrimonial Project v1.0 has unauthenticated SQL injection vulnerabilities in the view_profile.php resource. Attackers can execute arbitrary SQL commands without authentication, potentially compromising the entire database. All users running this specific version are affected.

💻 Affected Systems

Products:
  • Online Matrimonial Project
Versions: v1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in the default installation with no special configuration required.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data manipulation, authentication bypass, and potential remote code execution on the database server.

🟠

Likely Case

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

🟢

If Mitigated

Limited impact with proper input validation and database permissions, potentially only error messages or partial data exposure.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

SQL injection via 'id' parameter requires minimal technical skill to exploit.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://projectworlds.in

Restart Required: No

Instructions:

1. Check vendor website for updated version
2. Replace vulnerable view_profile.php file
3. Implement parameterized queries or input validation

🔧 Temporary Workarounds

Input Validation Filter

all

Add input validation to sanitize the 'id' parameter before database query

Add PHP code: if(!is_numeric($_GET['id'])) { die('Invalid input'); }

Web Application Firewall Rule

all

Block SQL injection patterns in the 'id' parameter

WAF rule: Block requests with SQL keywords in 'id' parameter

🧯 If You Can't Patch

  • Implement network segmentation to isolate the vulnerable system
  • Deploy a web application firewall with SQL injection protection rules

🔍 How to Verify

Check if Vulnerable:

Test view_profile.php?id=1' OR '1'='1 and observe database errors or unexpected behavior

Check Version:

Check project documentation or source code for version information

Verify Fix Applied:

Test with SQL injection payloads and verify proper error handling or rejection

📡 Detection & Monitoring

Log Indicators:

  • SQL syntax errors in application logs
  • Multiple failed parameter validation attempts
  • Unusual database query patterns

Network Indicators:

  • HTTP requests with SQL keywords in 'id' parameter
  • Abnormal request patterns to view_profile.php

SIEM Query:

source="web_logs" AND uri="*view_profile.php*" AND (param="*id=*'*" OR param="*id=*%27*")

🔗 References

📤 Share & Export