CVE-2022-32002

9.8 CRITICAL

📋 TL;DR

Badminton Center Management System v1.0 contains a SQL injection vulnerability in the admin panel's court management module. Attackers can exploit this to execute arbitrary SQL commands, potentially compromising the entire database. This affects all installations of the vulnerable software version.

💻 Affected Systems

Products:
  • Badminton Center Management System
Versions: v1.0
Operating Systems: Any OS running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Requires admin panel access, but SQL injection can bypass authentication if chained with other vulnerabilities.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data manipulation, authentication bypass, and potential server takeover via SQL injection to RCE chaining.

🟠

Likely Case

Database information disclosure, session hijacking, privilege escalation, and data manipulation affecting business operations.

🟢

If Mitigated

Limited impact if proper input validation, parameterized queries, and WAF rules are in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: HIGH

🎯 Exploit Status

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

Exploit requires admin access, but SQL injection payloads are well-documented and easy to weaponize.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available

Restart Required: No

Instructions:

No official patch available. Implement workarounds or migrate to alternative software.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Add server-side validation to sanitize the 'id' parameter in manage_court.php

Modify /bcms/admin/courts/manage_court.php to validate id parameter as integer

WAF Rule Implementation

all

Deploy web application firewall rules to block SQL injection patterns

Add WAF rule: deny requests containing SQL keywords like UNION, SELECT, INSERT, DELETE, DROP, OR 1=1

🧯 If You Can't Patch

  • Isolate the system behind a reverse proxy with strict input filtering
  • Implement network segmentation to limit database access from the web server

🔍 How to Verify

Check if Vulnerable:

Test the endpoint with SQL injection payload: /bcms/admin/courts/manage_court.php?id=1' OR '1'='1

Check Version:

Check software version in admin panel or readme files

Verify Fix Applied:

Test with same payload after fixes - should return error or no data disclosure

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL errors in web server logs
  • Multiple requests with SQL keywords in query parameters
  • Requests to manage_court.php with non-numeric id parameters

Network Indicators:

  • HTTP requests containing SQL injection patterns to the vulnerable endpoint
  • Unusual database query patterns from web server IP

SIEM Query:

source="web_logs" AND uri="/bcms/admin/courts/manage_court.php" AND (query="*UNION*" OR query="*SELECT*" OR query="*OR 1=1*")

🔗 References

📤 Share & Export