CVE-2025-26157

5.9 MEDIUM

📋 TL;DR

A SQL injection vulnerability in the Beauty Parlour Management System V1.1 allows remote attackers to execute arbitrary SQL commands via the 'name' parameter in POST requests to /bpms/index.php. This affects all deployments of this specific software version, potentially compromising database integrity and confidentiality.

💻 Affected Systems

Products:
  • Beauty Parlour Management System
Versions: V1.1
Operating Systems: Any OS running PHP and MySQL/MariaDB
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the specific file /bpms/index.php when handling POST requests with the 'name' parameter.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, data manipulation, or remote code execution if database functions allow command execution.

🟠

Likely Case

Unauthorized data access, data modification, or authentication bypass leading to privilege escalation.

🟢

If Mitigated

Limited impact with proper input validation and database permissions restricting query execution.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

SQL injection via POST parameter is straightforward to exploit with common tools like sqlmap.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: Not available

Restart Required: No

Instructions:

No official patch available. Implement workarounds or replace with secure software.

🔧 Temporary Workarounds

Input Validation Filter

all

Add server-side validation to sanitize the 'name' parameter before processing.

Edit /bpms/index.php to add: $name = mysqli_real_escape_string($conn, $_POST['name']);

Web Application Firewall Rule

all

Block SQL injection patterns in POST requests to /bpms/index.php.

ModSecurity rule: SecRule ARGS_POST:name "@detectSQLi" "id:1001,phase:2,deny"

🧯 If You Can't Patch

  • Isolate the system on a separate network segment with strict access controls.
  • Implement database-level protections: use least privilege accounts, enable query logging, and restrict database functions.

🔍 How to Verify

Check if Vulnerable:

Test with sqlmap: sqlmap -u "http://target/bpms/index.php" --data="name=test" --dbs

Check Version:

Check software version in admin panel or configuration files.

Verify Fix Applied:

Re-run sqlmap test; successful fix should show no SQL injection vulnerabilities.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts from single IP
  • POST requests to /bpms/index.php with SQL keywords in parameters

Network Indicators:

  • Unusual outbound database connections from web server
  • HTTP POST requests containing SQL syntax

SIEM Query:

source="web_logs" AND uri="/bpms/index.php" AND (POST_param="name" AND POST_value MATCHES "(?i)(union|select|insert|delete|update|drop|--|#|/*)")

🔗 References

📤 Share & Export