CVE-2022-31991

9.8 CRITICAL

📋 TL;DR

Badminton Center Management System v1.0 contains a SQL injection vulnerability in the delete_court function that allows attackers to execute arbitrary SQL commands. This affects all installations of the vulnerable software version. Attackers can potentially access, modify, or delete database content.

💻 Affected Systems

Products:
  • Badminton Center Management System
Versions: v1.0
Operating Systems: Any OS running PHP web server
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all installations of v1.0; requires PHP environment with database backend

📦 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 data access, modification of court booking data, potential privilege escalation

🟢

If Mitigated

Limited impact if proper input validation and WAF rules are in place

🌐 Internet-Facing: HIGH - The vulnerable endpoint is accessible via web interface
🏢 Internal Only: HIGH - Even internal systems are vulnerable to authenticated or unauthenticated attacks

🎯 Exploit Status

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

Public exploit details available in GitHub repository; SQL injection is straightforward to exploit

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: Not available

Restart Required: No

Instructions:

No official patch available. Consider replacing with alternative software or implementing custom fixes.

🔧 Temporary Workarounds

Input Validation and Parameterized Queries

all

Implement proper input validation and use parameterized queries in the delete_court function

Manual code modification required: Replace raw SQL with prepared statements

Web Application Firewall Rules

all

Block SQL injection patterns targeting the vulnerable endpoint

WAF-specific configuration to block patterns like UNION SELECT, OR 1=1, etc.

🧯 If You Can't Patch

  • Isolate the system behind a reverse proxy with strict WAF rules
  • Disable or restrict access to the vulnerable endpoint (/bcms/classes/Master.php?f=delete_court)

🔍 How to Verify

Check if Vulnerable:

Test the endpoint with SQL injection payloads: /bcms/classes/Master.php?f=delete_court&id=1' OR '1'='1

Check Version:

Check software version in admin panel or configuration files

Verify Fix Applied:

Test with same payloads; should return error or no database interaction

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL errors in web server logs
  • Multiple requests to delete_court endpoint with special characters

Network Indicators:

  • HTTP requests containing SQL keywords to vulnerable endpoint
  • Unusual database query patterns

SIEM Query:

web.url:*delete_court* AND (web.query:*UNION* OR web.query:*OR 1=1* OR web.query:*'--*)

🔗 References

📤 Share & Export