CVE-2025-11662
BaseFortify
Publication date: 2025-10-13
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 |
|---|---|---|
| mayurik | best_salon_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-11662 is a critical SQL injection vulnerability in the SourceCodester Best Salon Management System version 1.0, specifically in the /booking.php file. The vulnerability occurs because the 'serv_id' parameter is not properly validated or sanitized before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely without authentication, potentially manipulating the database in unauthorized ways. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to gain unauthorized access to your database, leading to data leakage, data tampering, and potentially full system control. It can compromise the confidentiality, integrity, and availability of your system, disrupt business operations, and cause service outages. The attack is easy to perform remotely and does not require authentication, increasing the risk of exploitation. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'serv_id' parameter in POST requests to /booking.php for SQL injection. Tools like sqlmap can be used to automate detection. For example, using sqlmap with the appropriate URL and POST data targeting 'serv_id[]' can confirm the vulnerability. Additionally, searching for the vulnerable endpoint using Google dorking with "inurl:booking.php" can help identify targets. Specific SQL injection techniques such as time-based blind, error-based, and boolean-based blind injections can be tested using payloads involving MySQL functions like RLIKE, GTID_SUBSET, and SLEEP. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements to ensure user inputs are treated as data and not executable SQL code, applying strict input validation and filtering on the 'serv_id' parameter to enforce expected formats, and minimizing database user permissions by avoiding high-privilege accounts for routine database operations. Regular security audits should also be conducted to detect and remediate vulnerabilities promptly. If possible, replacing the affected product with a secure alternative is recommended as no known countermeasures are documented. [1, 2]