CVE-2025-14711
SQL Injection in FantasticLBP Hotels Server Allows Remote Exploit
Publication date: 2025-12-15
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 |
|---|---|---|
| fantasticlbp | hotels_server | to 2019-03-23 (inc) |
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-14711 is a critical SQL injection vulnerability in the FantasticLBP Hotels_Server project, specifically in the /controller/api/hotelList.php file. It arises from improper validation and handling of user-supplied parameters such as 'pickedHotelName' and 'type', which are directly used in SQL queries without adequate sanitization. This flaw allows attackers to inject malicious SQL code remotely without authentication, enabling unauthorized access to the database, including reading, modifying, or deleting sensitive data. [1, 2, 3, 4, 5]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, allowing attackers to read, modify, or delete sensitive information. It can result in data leakage, data tampering, full system compromise, and potential service disruption. Since the attack can be performed remotely without authentication, it poses a severe risk to system security, data integrity, and business continuity. [1, 2, 3, 4, 5]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the vulnerable parameters `pickedHotelName` and `type` in the `/controller/api/hotelList.php` endpoint for SQL injection. A common method is to use the sqlmap tool to automate detection. For example, you can run a command like: ``` sqlmap.py -u "http://hotelsserver/controller/api/HotelList.php" --data="key=TheHotelReversationApplication&request=5&pickedHotelName=ι εΊ&cityName=εδΊ¬&page=1&size=10&pickedStar=x&pickedPrice=x" -p pickedHotelName --current-db --batch ``` This command tests the `pickedHotelName` parameter for SQL injection vulnerabilities. Similar testing can be done targeting the `type` parameter by adjusting the payload accordingly. Additionally, vulnerable targets can be discovered using Google dorking with queries like `inurl:controller/api/hotelList.php` to identify exposed endpoints. These detection methods help confirm the presence of the SQL injection flaw. [3, 4, 5]
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 attacks. 2. Enforce strict input validation and filtering on the `pickedHotelName` and `type` parameters to ensure inputs conform to expected formats. 3. Minimize database user privileges by avoiding the use of high-privilege accounts (such as root or admin) for routine database operations. 4. Conduct regular security audits of the code and systems to detect and remediate vulnerabilities promptly. If possible, consider replacing the affected component with an alternative product, as no official patches or mitigations have been provided by the vendor. These steps aim to protect system security and maintain data integrity. [3, 4, 5]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows unauthorized access, modification, and deletion of sensitive data through SQL injection, which can lead to data breaches and compromise data integrity and confidentiality. Such security failures can result in non-compliance with common standards and regulations like GDPR and HIPAA, which mandate protection of personal and sensitive data. Therefore, exploitation of this vulnerability could cause violations of these regulations due to unauthorized data exposure and lack of adequate security controls. [1, 2, 3, 4, 5]