Skip to main content
CVE-2025-9831VulnerabilityPublished

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

Affects PHPGurukul Beauty Parlour Management SystemSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 06:26 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 36% 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
PHPGurukul Beauty Parlour Management SystemAffected
  • =1.1
Fixed in–

AI-suggested

Organizations should immediately audit their use of PHPGurukul Beauty Parlour Management System 1.1 and restrict access to the /admin/edit-services.php endpoint to trusted internal networks only, using network segmentation and firewall rules. Input validation and parameterized queries should be implemented or verified in the application code to prevent SQL injection. If vendor patches or updates become available, they should be applied without delay. In the absence of official patches, deploying Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the 'sername' parameter can provide interim protection. Regular database backups and monitoring for unusual query patterns or access attempts should be established to detect exploitation attempts early. Additionally, organizations should review and limit database user privileges to minimize the impact of potential SQL injection attacks. Conducting security assessments and penetration testing focused on this vulnerability can help validate the effectiveness of mitigations.

Description

A weakness has been identified in PHPGurukul Beauty Parlour Management System 1.1. This impacts an unknown function of the file /admin/edit-services.php. This manipulation of the argument sername causes sql injection. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be exploited.

References

Community reviews

Loading reviews…