Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-10402: SQL Injection in PHPGurukul Beauty Parlour Management System

0
Medium
VulnerabilityCVE-2025-10402cvecve-2025-10402
Published: Sun Sep 14 2025 (09/14/2025, 16:32:07 UTC)
Source: CVE Database V5
Vendor/Project: PHPGurukul
Product: Beauty Parlour Management System

Description

A flaw has been found in PHPGurukul Beauty Parlour Management System 1.1. The impacted element is an unknown function of the file /admin/readenq.php. Executing manipulation of the argument delid can lead to sql injection. The attack can be executed remotely. The exploit has been published and may be used.

AI-Powered Analysis

AILast updated: 09/22/2025, 00:31:29 UTC

Technical Analysis

CVE-2025-10402 is a SQL Injection vulnerability identified in version 1.1 of the PHPGurukul Beauty Parlour Management System, specifically within the /admin/readenq.php file. The vulnerability arises from improper sanitization or validation of the 'delid' parameter, which is manipulated by an attacker to inject malicious SQL commands. This flaw allows remote attackers to execute arbitrary SQL queries on the backend database without requiring any authentication or user interaction. The vulnerability is classified with a CVSS 4.0 base score of 6.9, indicating a medium severity level. The attack vector is network-based (AV:N), with low attack complexity (AC:L), no privileges required (PR:N), and no user interaction needed (UI:N). The impact affects confidentiality, integrity, and availability to a limited extent (VC:L, VI:L, VA:L). Exploitation could lead to unauthorized data disclosure, data modification, or deletion, potentially compromising sensitive customer and business data managed by the system. Although no known exploits are currently reported in the wild, the existence of a published exploit increases the risk of exploitation. The vulnerability affects only version 1.1 of the product, which is a niche management system targeted at beauty parlours, likely deployed in small to medium-sized businesses. The lack of available patches or official remediation increases the urgency for affected organizations to implement mitigations.

Potential Impact

For European organizations using PHPGurukul Beauty Parlour Management System 1.1, this vulnerability poses a significant risk to the confidentiality and integrity of customer and business data. Exploitation could result in unauthorized access to personal data, potentially violating GDPR requirements and leading to regulatory penalties. Data tampering or deletion could disrupt business operations, causing financial loss and reputational damage. Since the system is used in the beauty and wellness sector, which often handles sensitive client information such as contact details and appointment histories, the breach could erode customer trust. The remote and unauthenticated nature of the attack vector means that attackers can exploit this vulnerability from anywhere, increasing the threat surface. Although the product is niche, any European country with a higher concentration of small and medium enterprises in the beauty industry using this software could face localized impacts. The medium severity rating suggests that while the threat is serious, it may not lead to full system compromise or widespread disruption without additional attack steps.

Mitigation Recommendations

Given the absence of official patches, European organizations should immediately implement compensating controls. First, restrict network access to the /admin/readenq.php endpoint by IP whitelisting or VPN-only access to limit exposure. Employ web application firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the 'delid' parameter. Conduct thorough input validation and sanitization on all user-supplied inputs, especially the 'delid' parameter, using parameterized queries or prepared statements if possible. If source code access is available, refactor the vulnerable code to eliminate direct concatenation of user inputs into SQL queries. Regularly monitor logs for suspicious database query patterns or failed injection attempts. Additionally, organizations should consider migrating to alternative, actively maintained management systems with better security postures. Finally, maintain up-to-date backups of all critical data to enable recovery in case of data corruption or deletion.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-09-13T19:41:22.557Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68c6ef1f5673b0861add6118

Added to database: 9/14/2025, 4:36:47 PM

Last enriched: 9/22/2025, 12:31:29 AM

Last updated: 10/30/2025, 8:51:36 AM

Views: 51

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats