VulnerabilityPublished 8 Oct 2025Updated 24 Feb 2026

CVE-2025-11507: 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, 10:12 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 35% 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

Immediately restrict access to the /admin/search-invoices.php endpoint by IP whitelisting or VPN-only access to reduce exposure.
Implement strict input validation and sanitization on the 'searchdata' parameter, ensuring that only expected input formats are accepted.
Refactor the code to use parameterized queries or prepared statements to prevent SQL injection.
Conduct a thorough security review of the entire application to identify and remediate similar injection flaws.
Monitor logs for suspicious query patterns or repeated failed attempts indicative of exploitation attempts.
If possible, isolate the database with least privilege principles, ensuring the web application user has minimal rights.
Backup all critical data regularly to enable recovery in case of compromise.
Engage with the vendor or community to obtain or develop patches and apply them promptly once available.
Educate staff on the risks and signs of exploitation to improve detection and response.
Consider deploying web application firewalls (WAFs) with SQL injection detection rules as an interim protective measure.

Description

A weakness has been identified in PHPGurukul Beauty Parlour Management System 1.1. The impacted element is an unknown function of the file /admin/search-invoices.php. This manipulation of the argument searchdata causes sql injection. The attack can be initiated remotely. The exploit has been made available to the public and could be used for attacks.

Impact

The SQL injection vulnerability allows attackers to execute arbitrary SQL commands on the backend database, potentially leading to unauthorized disclosure of sensitive customer and business data, data tampering, or deletion. This can compromise the confidentiality, integrity, and availability of the affected system. For organizations, this could result in data breaches involving client personal information, financial records, and transaction histories, damaging reputation and incurring regulatory penalties. Attackers could also leverage this vulnerability to pivot further into internal networks if the management system is connected to broader IT infrastructure. Since the vulnerability requires no authentication or user interaction, it is highly accessible to remote attackers scanning for vulnerable instances. The public availability of exploit code increases the likelihood of opportunistic attacks, especially targeting small businesses that may lack robust cybersecurity defenses. The impact is particularly significant for businesses relying on this system for daily operations, as disruption or data loss could affect service continuity and customer trust.

Summary

CVE-2025-11507 identifies a SQL injection vulnerability in the PHPGurukul Beauty Parlour Management System version 1.1. The vulnerability exists in the /admin/search-invoices.php script, where the 'searchdata' parameter is not properly sanitized before being used in SQL queries. This allows an unauthenticated remote attacker to manipulate the SQL query logic by injecting crafted input, potentially leading to unauthorized data access, data modification, or database compromise. The vulnerability requires no authentication or user interaction, making it easily exploitable over the network. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P) indicates network attack vector, low attack complexity, no privileges or user interaction needed, and partial impacts on confidentiality, integrity, and availability. Although the impact is partial, the exploitability and public availability of exploit code increase the threat level. No official patches or mitigations have been released by the vendor as of the publication date. The vulnerability affects only version 1.1 of the product, which is a niche management system used primarily by small and medium beauty parlour businesses. The lack of segmentation or hardened access controls in typical deployments may exacerbate the risk. This vulnerability is a classic example of improper input validation leading to SQL injection, a common and dangerous web application security flaw.

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