CVE-2025-10403
BaseFortify
Publication date: 2025-09-14
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?
This vulnerability is a critical SQL injection flaw in PHPGurukul Beauty Parlour Management System version 1.1, specifically in the /admin/view-enquiry.php file. It occurs because the 'viewid' parameter is not properly sanitized or validated before being used in SQL queries. This allows remote attackers to inject malicious SQL commands, potentially manipulating the database without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, data tampering, full system control, and potential service disruption. Attackers can read, modify, or delete sensitive information, impacting the confidentiality, integrity, and availability of the system. The attack can be performed remotely without any authentication, making it easy to exploit. [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 'viewid' parameter in the /admin/view-enquiry.php page for SQL injection. You can use SQL injection payloads such as time-based blind SQL injection (e.g., viewid=2 AND (SELECT SLEEP(5))) or UNION-based SQL injection payloads to check for injection points. Tools like sqlmap can automate detection by targeting the URL with the vulnerable parameter. Additionally, Google dorking with queries like 'inurl:admin/view-enquiry.php' can help identify vulnerable instances on your network or externally. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Apply strict input validation and filtering on the 'viewid' parameter to ensure it only accepts expected formats (e.g., numeric values). 3) Limit database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. 4) If possible, replace the affected product with a secure alternative. These steps help prevent exploitation and reduce risk. [1, 2, 3]