CVE-2025-14710
SQL Injection in FantasticLBP OrderList.php Enables Remote Attack
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-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-14710 is a critical Boolean-based Blind SQL injection vulnerability in the FantasticLBP Hotels Server, specifically in the /controller/api/OrderList.php file. It occurs due to improper handling of the 'telephone' parameter, which is directly used in SQL queries without adequate input validation or sanitization. This allows attackers to inject malicious SQL code remotely without authentication, enabling unauthorized manipulation of database queries. The flaw corresponds to CWE-89 and can lead to unauthorized data access, data leakage, data tampering, and potential full system compromise. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, modification or deletion of data, full system control by attackers, and disruption of service availability. Since exploitation requires no authentication and can be performed remotely, attackers can easily compromise confidentiality, integrity, and availability of the affected system. This can lead to data breaches, loss of business continuity, and potential financial and reputational damage. [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 'telephone' parameter in the /controller/api/OrderList.php endpoint for SQL injection. A commonly used tool is sqlmap. An example command to test this vulnerability is: python sqlmap.py -u "http://hotelsserver/controller/api/OrderList.php" --data="telephone=13800138000&page=1&size=10" -p telephone --current-db --batch. Additionally, vulnerable targets can be identified using Google dorking with the query: inurl:controller/api/OrderList.php. [1, 2, 3]
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) Enforce strict input validation and filtering to ensure user data conforms to expected formats. 3) Minimize database user permissions by avoiding use of high-privilege accounts (e.g., root or admin) for routine operations. 4) Conduct regular security audits of code and systems to detect and address vulnerabilities promptly. Since no vendor patch or countermeasure is available, replacing the affected component with an alternative product is also suggested. [1, 2, 3]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows unauthorized remote attackers to perform SQL injection attacks, potentially leading to unauthorized access, data leakage, and data manipulation. Such breaches of confidentiality and integrity can result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information. Therefore, the vulnerability poses a significant risk to compliance with these common standards and regulations. [1, 2, 3]