CVE-2025-9830
BaseFortify
Publication date: 2025-09-02
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| phpgurukul | beauty_parlour_management_system | 1.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-9830 is a critical SQL injection vulnerability in PHPGurukul Beauty Parlour Management System version 1.1, specifically in the /admin/add-customer-services.php file. The vulnerability arises because the sids[] parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, potentially leading to data leakage, modification, or deletion. The attack can be executed remotely without authentication, and a public exploit is available. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, allowing attackers to retrieve, modify, or delete sensitive data. It can also enable attackers to gain full system control and disrupt services. Since the attack requires no authentication and can be performed remotely, it poses a significant risk to data confidentiality, integrity, and availability. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /admin/add-customer-services.php endpoint for SQL injection via the sids[] parameter. Tools like sqlmap can be used to automate detection, for example: sqlmap -u "http://target/admin/add-customer-services.php" --data="sids[]=1" --batch. Additionally, Google dorking can help identify vulnerable targets using queries like: inurl:admin/add-customer-services.php. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, applying rigorous input validation and filtering on the sids[] parameter, and minimizing database user permissions by avoiding high-privilege accounts for routine operations. If possible, replace or update the affected component. Restricting access to the vulnerable endpoint and monitoring for suspicious activity are also recommended. [1, 2, 3]