CVE-2025-15127VulnerabilityPublished 28 Dec 2025Updated 29 Dec 2025

CVE-2025-15127: FantasticLBP Hotels_Server · SQL Injection

Affects FantasticLBP Hotels_ServerSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 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 28 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

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 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

Given the lack of vendor patches, European organizations should implement immediate compensating controls. First, apply strict input validation and sanitization on the hotelId parameter at the application or web server level to prevent malicious SQL payloads. Deploy Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection patterns targeting the vulnerable endpoint. Conduct thorough code reviews and consider temporary disabling or restricting access to the /controller/api/Room.php API if feasible. Monitor database logs and network traffic for unusual queries or access patterns indicative of exploitation attempts. Employ database-level protections such as least privilege access controls and query parameterization where possible. Organizations should also prepare incident response plans specific to SQL injection attacks and maintain up-to-date backups to enable recovery from potential data tampering. Engage with the vendor continuously for updates and consider alternative software solutions if the vendor remains unresponsive.

Description

A security vulnerability has been detected in FantasticLBP Hotels_Server up to 67b44df162fab26df209bd5d5d542875fcbec1d0. Affected by this issue is some unknown functionality of the file /controller/api/Room.php. Such manipulation of the argument hotelId leads to sql injection. The attack may be launched remotely. The exploit has been disclosed publicly and may be used. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, the impact of this vulnerability can be significant, especially for those in the hospitality and travel sectors using FantasticLBP Hotels_Server. Exploitation could lead to unauthorized access to sensitive customer data such as personal identification, booking details, and payment information, violating GDPR and other data protection regulations. Integrity of booking data could be compromised, leading to fraudulent bookings or cancellations, disrupting business operations and customer trust. Availability impacts, while limited, could still result in service outages or degraded performance if attackers execute denial-of-service style SQL queries. The public disclosure and absence of vendor patches increase the urgency for European entities to implement mitigations to avoid potential regulatory penalties, financial losses, and reputational harm. Additionally, attackers could leverage this vulnerability as a foothold for further network intrusion or lateral movement within affected organizations.

Summary

CVE-2025-15127 identifies a SQL injection vulnerability in the FantasticLBP Hotels_Server product, specifically within the /controller/api/Room.php endpoint. The vulnerability arises due to insufficient sanitization of the hotelId parameter, allowing attackers to inject malicious SQL code remotely without authentication or user interaction. This injection can manipulate backend database queries, potentially exposing sensitive hotel booking data, customer information, or enabling unauthorized data modification and deletion. The product operates on a rolling release model, complicating version tracking and patch management, and the vendor has not issued any response or patch following early disclosure. The vulnerability has been publicly disclosed, increasing the risk of exploitation despite no current known active exploits. The CVSS 4.0 vector indicates a network-based attack with low complexity and no required privileges, impacting confidentiality, integrity, and availability to a limited extent. This vulnerability is critical for organizations relying on FantasticLBP Hotels_Server for managing hotel room bookings and related services, as exploitation could lead to data breaches, service interruptions, or reputational damage. The lack of vendor response necessitates immediate defensive measures by users of the software.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 30 Dec 2025, 23:43 UTC

Technical details

References

Community reviews

Related threats