CVE-2025-10403

7.3 HIGH

📋 TL;DR

This vulnerability allows remote attackers to execute SQL injection attacks against PHPGurukul Beauty Parlour Management System 1.1 by manipulating the 'viewid' parameter in the /admin/view-enquiry.php file. This can lead to unauthorized database access, data theft, or system compromise. Organizations using this specific version of the software are affected.

💻 Affected Systems

Products:
  • PHPGurukul Beauty Parlour Management System
Versions: 1.1
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in the default installation and requires no special configuration to be exploitable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data exfiltration, privilege escalation, and potential remote code execution on the underlying server.

🟠

Likely Case

Unauthorized access to sensitive customer and business data stored in the database, including personal information and financial records.

🟢

If Mitigated

Limited impact with proper input validation and database permissions, potentially only allowing data viewing without modification.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit details are publicly available on GitHub, making this easily exploitable by attackers with basic SQL injection knowledge.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://phpgurukul.com/

Restart Required: No

Instructions:

No official patch available. Consider implementing input validation and parameterized queries in the affected file.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Add input validation and sanitization for the 'viewid' parameter in /admin/view-enquiry.php

Edit /admin/view-enquiry.php to validate that 'viewid' contains only numeric characters before using in SQL queries

Web Application Firewall (WAF)

all

Deploy a WAF with SQL injection protection rules

🧯 If You Can't Patch

  • Isolate the system from the internet and restrict access to authorized users only
  • Implement network segmentation to limit database server access from the web application

🔍 How to Verify

Check if Vulnerable:

Check if /admin/view-enquiry.php exists and accepts 'viewid' parameter without proper validation

Check Version:

Check the software version in the application interface or configuration files

Verify Fix Applied:

Test SQL injection attempts against the 'viewid' parameter to ensure they are blocked

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts from the same IP
  • Suspicious parameter values in web server logs

Network Indicators:

  • SQL injection patterns in HTTP requests to /admin/view-enquiry.php
  • Unusual database connection patterns

SIEM Query:

source="web_server" AND uri="/admin/view-enquiry.php" AND (param="viewid" AND value MATCHES "[';]|UNION|SELECT")

🔗 References

📤 Share & Export