CVE-2025-13208VulnerabilityPublished 15 Nov 2025Updated 17 Nov 2025

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

Affects FantasticLBP Hotels ServerSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.3Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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: Low
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
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 Nov 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-26.

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

These include deploying Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting subjectId and cityName parameters. Input validation and sanitization should be enforced at the application or proxy level to reject suspicious input patterns. Organizations should conduct thorough code reviews and penetration testing to identify and remediate injection points if source code access is available. Network segmentation can limit attacker movement if exploitation occurs. Monitoring and alerting on unusual database queries or application logs can provide early detection of exploitation attempts. Additionally, organizations should prepare incident response plans specific to this vulnerability and consider temporary disabling or restricting access to the affected API endpoint if feasible. Maintaining regular backups of critical data will aid recovery if data integrity is compromised. Finally, organizations should engage with the vendor for updates and track threat intelligence feeds for emerging exploits or patches.

Description

A security flaw has been discovered in FantasticLBP Hotels Server up to 67b44df162fab26df209bd5d5d542875fcbec1d0. The impacted element is an unknown function of the file controller/api/hotelList.php. The manipulation of the argument subjectId/cityName results in sql injection. The attack can be executed remotely. The exploit has been released to the public and may be exploited. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, this vulnerability poses a risk of unauthorized access to sensitive customer and booking data, potentially leading to data breaches and violations of GDPR regulations. The integrity of reservation data could be compromised, resulting in fraudulent bookings or cancellations, damaging business operations and reputation. Availability of the Hotels Server could also be affected if attackers exploit the vulnerability to execute destructive SQL commands. Given the public availability of an exploit and absence of vendor patches, attackers may rapidly target vulnerable systems. This is particularly impactful for tourism-dependent economies and hospitality providers in Europe, where customer trust and data protection are critical. Additionally, compromised systems could be used as footholds for broader network intrusion or lateral movement within enterprise environments. The medium severity rating indicates a moderate but tangible risk that requires immediate attention to avoid operational and compliance consequences.

Summary

CVE-2025-13208 identifies a SQL injection vulnerability in the FantasticLBP Hotels Server product, specifically within an unknown function in the controller/api/hotelList.php file. The vulnerability is triggered by manipulating the subjectId or cityName parameters, which are not properly sanitized before being used in SQL queries. This allows remote attackers to inject arbitrary SQL commands, potentially extracting or modifying sensitive data stored in the backend database. The attack vector requires no authentication or user interaction, making it easier to exploit remotely. The product follows a rolling release model, complicating version tracking and patch management. Despite early notification, the vendor has not responded or issued a patch, and a public exploit is available, increasing the threat landscape. The CVSS 4.0 score of 5.3 reflects a medium severity, considering the ease of exploitation and potential impact on confidentiality, integrity, and availability, though privileges required are low and no user interaction is needed. The vulnerability could be leveraged to access customer data, booking information, or disrupt hotel operations, posing significant risks to organizations relying on this software. The lack of vendor support and patch availability necessitates proactive defensive measures by users.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 22 Nov 2025, 19:26 UTC

Technical details

References

Community reviews

Related threats