CVE-2025-9930
BaseFortify
Publication date: 2025-09-04
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 |
|---|---|---|
| 1000projects | beauty_parlour_management_system | 1.0 |
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-9930 is a critical SQL injection vulnerability in version 1.0 of the Beauty Parlour Management System, specifically in the /admin/contact-us.php file. It occurs because the 'mobnumber' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to your database, resulting in data leakage, modification, or deletion. Attackers can compromise the confidentiality, integrity, and availability of your system. It may also lead to full system compromise or service disruption, threatening business continuity and security. [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 checking for the presence of the vulnerable file /admin/contact-us.php in the Beauty Parlour Management System version 1.0 and testing the 'mobnumber' parameter for SQL injection. Attackers can identify vulnerable targets using Google dorking with queries like: inurl:admin/contact-us.php. For active testing, one could use tools like sqlmap to test the 'mobnumber' parameter for SQL injection by sending crafted payloads to the URL. Example command with sqlmap: sqlmap -u "http://target/admin/contact-us.php?mobnumber=1" --batch --dbs [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements to safely handle user inputs, strictly validating and filtering all user input to ensure it matches expected formats, and minimizing database user permissions by avoiding the use of high-privilege accounts for routine operations. Additionally, conducting regular security audits to detect and remediate vulnerabilities promptly is recommended. If possible, replacing the affected product with an alternative solution is suggested due to the lack of known countermeasures. [2, 3]