VulnerabilityPublished 8 Oct 2025Updated 24 Feb 2026

CVE-2025-11505: PHPGurukul Beauty Parlour Management System · SQL Injection

Affects PHPGurukul Beauty Parlour Management SystemSource CVE Database V5

Public exploit available · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
PHPGurukul Beauty Parlour Management System	Affected =1.1	Fixed in–

AI-suggested

Organizations using PHPGurukul Beauty Parlour Management System version 1.1 should immediately review and restrict access to the /admin/new-appointment.php endpoint, ideally limiting it to trusted IP addresses or internal networks. Implementing a web application firewall (WAF) with SQL injection detection and prevention rules can help block exploit attempts. Until an official patch is released, administrators should audit and sanitize all input parameters, especially delid, to prevent injection. Employing parameterized queries or prepared statements in the application code is a best practice to eliminate injection risks. Regularly monitoring logs for suspicious activity related to the delid parameter is recommended. Additionally, organizations should consider isolating the management system from the internet or placing it behind VPN access to reduce exposure. Finally, backing up databases frequently and securely will aid in recovery if an attack occurs.

Description

A vulnerability was identified in PHPGurukul Beauty Parlour Management System 1.1. Impacted is an unknown function of the file /admin/new-appointment.php. The manipulation of the argument delid leads to sql injection. It is possible to initiate the attack remotely. The exploit is publicly available and might be used.

Impact

The primary impact of this vulnerability is unauthorized access to the backend database of the affected management system. Attackers could extract sensitive customer data, appointment details, or internal business information, leading to confidentiality breaches. Additionally, attackers might alter or delete records, impacting data integrity and disrupting business operations. For organizations relying on this system, such data compromise could result in reputational damage, regulatory penalties (especially if personal data is involved), and financial losses. Since the vulnerability allows remote exploitation without authentication, attackers can launch automated attacks at scale, increasing the risk of widespread compromise among users of this software. However, the overall impact is somewhat limited by the niche nature of the product and its deployment primarily in small businesses, which may have less critical data but also fewer resources for incident response.

Summary

CVE-2025-11505 identifies a SQL injection vulnerability in the PHPGurukul Beauty Parlour Management System version 1.1. The vulnerability is located in the /admin/new-appointment.php script, where the delid parameter is improperly sanitized, allowing an attacker to inject malicious SQL queries. This injection flaw can be exploited remotely without requiring authentication or user interaction, making it highly accessible to attackers. The vulnerability can lead to unauthorized data access, modification, or deletion within the backend database, compromising confidentiality, integrity, and potentially availability of the system. The CVSS 4.0 score of 6.9 reflects a medium severity, considering the ease of exploitation (network accessible, no privileges required) but limited scope and impact due to the niche application. No official patches have been released yet, and while no active exploitation has been observed, public exploit code availability increases the risk. The vulnerability primarily affects installations of version 1.1 of this specific management system, which is typically deployed in small to medium beauty parlour businesses. The lack of authentication requirement and remote exploitability make this a significant risk for affected organizations.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:00 UTC

Technical details

References

Community reviews

Related threats