CVE-2025-9814
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-9814 is a critical SQL injection vulnerability in the PHPGurukul Beauty Parlour Management System version 1.1, specifically in the /admin/contact-us.php file. The vulnerability occurs because the 'mobnumber' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized manipulation of the database through crafted input, potentially leading to unauthorized data access, modification, or deletion. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, data leakage, data tampering, full system compromise, and disruption of services. Attackers can remotely execute arbitrary SQL commands without authentication, compromising the confidentiality, integrity, and availability of the system and its data. This poses significant risks to system security and business continuity. [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/contact-us.php endpoint for SQL injection via the mobnumber parameter. You can use tools like sqlmap to automate detection, for example: sqlmap -u "http://target/admin/contact-us.php" --data="mobnumber=1" --risk=3 --level=5. Additionally, manual testing can be done by injecting SQL payloads into the mobnumber parameter and observing the response for SQL errors or unexpected behavior. Google dorking with the query inurl:admin/contact-us.php can help identify vulnerable targets. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements to handle the mobnumber parameter, ensuring user inputs are treated strictly as data and not executable SQL code. Rigorous input validation and filtering should be applied to the mobnumber parameter to ensure it conforms to expected formats. Additionally, minimize database user permissions by avoiding the use of high-privilege accounts for routine database operations. If possible, replace or update the affected component or product to a version without this vulnerability. [3, 2, 1]