External risk intelligence

Phpgurukul Beauty Parlour Management System SQL Injection Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2024-51065

The vulnerability exists in an admin login page of a web-based management system. Such applications are frequently deployed as internet-facing web portals to facilitate remote management and administration, making the login interface and its parameters reachable from the public internet.

SQL Injection

Phpgurukul Beauty Parlour Management System

1.1

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability has been identified in the Phpgurukul Beauty Parlour Management System, a widely used application. This issue, a form of SQL injection, could allow unauthorized access to sensitive data and potentially impact system operations if exploited. Given the system's administrative function, understanding its potential exposure is important for maintaining secure operations.

Unauthorized database access possible.
Affects a system for managing business operations.
Confirm if this system is used internally.

Attack Path

How an attacker could exploit the issue

An attacker could target the Beauty Parlour Management System by sending specially crafted requests to the admin login page. If the system is exposed to the internet, an unauthenticated attacker could potentially exploit a weakness in how the username is handled on the `admin/index.php` page. This could allow them to manipulate database queries, leading to severe consequences.

No authentication required.
Inputting malicious data into username.
Full database compromise possible.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an attacker could exploit this vulnerability to gain unauthorized access to the Beauty Parlour Management System by manipulating the username parameter in the admin login. This could potentially allow them to view, modify, or delete sensitive system and user data.

Admin access and system data.
Via manipulated username parameter.
Unauthorized data access and modification.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Phpgurukul Beauty Parlour Management System is likely managed by the application owner or a dedicated platform team, with network and security teams responsible for exposure. The immediate priority is to identify all instances of this software, assess their reachability and criticality, and then confirm the accountable owner before planning remediation.

Application owner to take primary responsibility.
Verify external reachability and business criticality.
Plan remediation with vendor and affected teams.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is Phpgurukul Beauty Parlour Management System?

It is a web-based software application designed to help salon owners manage daily business operations, such as appointment scheduling, service tracking, and staff management. It acts as a central digital hub for administrative tasks, which is why it includes a specialized login area for managers to oversee the database.

What is the weakness in CVE-2024-51065?

This vulnerability is classified as SQL Injection (CWE-89). It happens when the software fails to properly sanitize input before using it in a database query. In this case, an attacker can input specially crafted text into the username field to trick the system's database into executing unauthorized commands, potentially granting full access to system data.

How can an attacker trigger this vulnerability?

An attacker triggers this by sending a request containing malicious SQL commands directly to the username parameter on the admin/index.php login page. Notably, the system does not require the attacker to be logged in to initiate this, meaning the exploit path relies on simply reaching that specific input field with a crafted request.

Is my system at risk if it is not on the internet?

Halo Surface Signal indicates this application is often deployed as an internet-facing portal, which significantly increases risk. If your instance is hosted only on a restricted internal network without public access, the likelihood of an external attacker reaching the vulnerable login page is greatly reduced, though internal security best practices should still apply.

What should I do if I am running this software?

First, locate and inventory all instances of this application within your environment. Verify whether these instances are accessible from the public internet, as these are the highest priority. Identify the owner responsible for the software and coordinate with them to assess the system's business criticality while you work toward a secure resolution.

References

github.com/0x1c1ph3r/CVEs/tree/main/CVE-2024-51065

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.