CVE-2025-11662

7.3 HIGH

📋 TL;DR

This CVE describes a SQL injection vulnerability in SourceCodester Best Salon Management System 1.0. Attackers can manipulate the serv_id parameter in /booking.php to execute arbitrary SQL commands remotely. Any organization using this specific software version is affected.

💻 Affected Systems

Products:
  • SourceCodester Best Salon Management System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects the specific version 1.0 of this salon management system.

📦 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, data manipulation, and potential privilege escalation within the application.

🟢

If Mitigated

Limited impact with proper input validation, parameterized queries, and database permissions restricting damage to non-critical data.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Public exploit code exists on GitHub, making exploitation trivial for attackers with basic SQL injection knowledge.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://www.sourcecodester.com/

Restart Required: No

Instructions:

No official patch available. Consider migrating to alternative software or implementing workarounds.

🔧 Temporary Workarounds

Input Validation Filter

all

Add server-side validation to only accept numeric values for serv_id parameter

Modify booking.php to include: if(!is_numeric($_GET['serv_id'])) { die('Invalid input'); }

WAF Rule Implementation

all

Deploy web application firewall rules to block SQL injection patterns targeting serv_id parameter

WAF-specific configuration to block patterns like: UNION SELECT, OR 1=1, --, ;, '

🧯 If You Can't Patch

  • Isolate the system behind a reverse proxy with strict input validation
  • Implement network segmentation to limit database access from the vulnerable application

🔍 How to Verify

Check if Vulnerable:

Test /booking.php?serv_id=1' OR '1'='1 and observe if SQL error or unexpected behavior occurs

Check Version:

Check application files or admin panel for version information

Verify Fix Applied:

Test with malicious inputs like serv_id=1' UNION SELECT 1,2,3-- and verify proper error handling or rejection

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL error messages in application logs
  • Multiple failed booking attempts with malformed serv_id parameters
  • Database queries with UNION, SELECT, or other injection patterns

Network Indicators:

  • HTTP requests to /booking.php with SQL keywords in parameters
  • Unusual database connection patterns from application server

SIEM Query:

source="web_logs" AND uri_path="/booking.php" AND (param="*serv_id=*'*" OR param="*serv_id=*UNION*" OR param="*serv_id=*SELECT*")

🔗 References

📤 Share & Export