VulnerabilityPublished 15 Dec 2025

CVE-2025-14711: FantasticLBP Hotels Server · SQL Injection

Affects FantasticLBP Hotels ServerSource CVE Database V5

Public exploit available · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

First, deploy web application firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the 'pickedHotelName/type' parameter. Conduct thorough input validation and sanitization on all user-supplied data, especially parameters interacting with databases. Review and harden database permissions to limit the impact of potential SQL injection attacks, ensuring the application uses least privilege principles. Monitor database logs and application behavior for unusual queries or anomalies indicative of exploitation attempts. Consider isolating the affected service within segmented network zones to reduce lateral movement risks. Engage in threat hunting and incident response preparedness focused on this vulnerability. Finally, maintain communication with the vendor for updates and plan for patch deployment once available. Organizations should also review their incident response and data breach notification procedures to comply with GDPR requirements in case of compromise.

Description

A flaw has been found in FantasticLBP Hotels Server up to 67b44df162fab26df209bd5d5d542875fcbec1d0. This vulnerability affects unknown code of the file /controller/api/hotelList.php. This manipulation of the argument pickedHotelName/type causes sql injection. The attack is possible to be carried out remotely. The exploit has been published and may be used. This product adopts a rolling release strategy to maintain continuous delivery The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, particularly those in the hospitality and tourism sectors using FantasticLBP Hotels Server, this vulnerability poses a significant risk. Successful exploitation could lead to unauthorized access to sensitive customer and business data, including booking details and personal information, violating GDPR and other data protection regulations. Data integrity could be compromised by unauthorized modifications, potentially causing operational disruptions and financial losses. Availability impacts could arise if attackers execute destructive SQL commands, leading to service outages. Given the remote, unauthenticated nature of the exploit, attackers could target multiple organizations en masse, increasing the threat landscape. The lack of vendor response and patches exacerbates the risk, forcing organizations to rely on interim mitigations. European entities with large volumes of hotel data and online booking systems are particularly vulnerable to reputational damage and regulatory penalties if exploited.

Summary

CVE-2025-14711 identifies a SQL injection vulnerability in the FantasticLBP Hotels Server, a software product used to manage hotel-related data and services. The vulnerability exists in the /controller/api/hotelList.php endpoint, where the 'pickedHotelName/type' parameter is improperly sanitized, allowing attackers to inject malicious SQL queries. This flaw enables remote exploitation without requiring authentication or user interaction, increasing its risk profile. The vulnerability affects the version identified by commit 67b44df162fab26df209bd5d5d542875fcbec1d0. The CVSS v4.0 score is 6.9 (medium), reflecting the network attack vector, low complexity, no privileges or user interaction needed, but limited impact on confidentiality, integrity, and availability. While no known exploits in the wild have been reported, the public availability of an exploit increases the likelihood of future attacks. Attackers exploiting this vulnerability could extract sensitive hotel data, manipulate booking information, or disrupt service availability by executing arbitrary SQL commands on the backend database. This could lead to data breaches, financial loss, and reputational damage for affected organizations.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 22 Dec 2025, 08:35 UTC

Technical details

References

Community reviews

Related threats