CVE-2025-9829: PHPGurukul Beauty Parlour Management System · SQL Injection
Affects PHPGurukul Beauty Parlour Management SystemSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% 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:PExploitation evidence
Disclosed: evidence found.
CVE published 2 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PHPGurukul Beauty Parlour Management System | Affected
| Fixed in– |
AI-suggested
1. Immediate mitigation should include restricting external access to the /signup.php endpoint via web application firewalls (WAFs) or network access controls to limit exposure. 2. Implement input validation and parameterized queries (prepared statements) in the signup module to prevent SQL injection. 3. Conduct a comprehensive code review of all input handling in the application, especially other parameters that might be vulnerable. 4. Monitor web server and database logs for suspicious queries or unusual activity targeting the 'mobilenumber' parameter or signup functionality. 5. If possible, upgrade to a patched version once available or consider migrating to alternative management systems with better security track records. 6. Educate staff about the risks and ensure regular backups of databases to enable recovery in case of data tampering. 7. Deploy runtime application self-protection (RASP) tools to detect and block injection attempts in real time. 8. For organizations unable to patch immediately, consider deploying virtual patching rules on WAFs to block known exploit patterns.
Description
A vulnerability was identified in PHPGurukul Beauty Parlour Management System 1.1. The impacted element is an unknown function of the file /signup.php. The manipulation of the argument mobilenumber leads to sql injection. Remote exploitation of the attack is possible. The exploit is publicly available and might be used. Other parameters might be affected as well.