CVE-2025-14207VulnerabilityPublished 8 Dec 2025

CVE-2025-14207: tushar-2223 Hotel-Management-System · SQL Injection

Affects tushar-2223 Hotel-Management-SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score

6.9Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 22% 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 8 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-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

Organizations should immediately audit their use of the tushar-2223 Hotel-Management-System and identify if the vulnerable version is deployed. Since the product uses a rolling release model without clear versioning, direct vendor communication is essential to obtain the latest secure build or patches. In the interim, implement strict input validation and sanitization on the 'ID' parameter in /admin/invoiceprint.php to prevent SQL injection. Employ parameterized queries or prepared statements to eliminate direct SQL concatenation. Deploy web application firewalls (WAFs) with rules targeting SQL injection patterns to detect and block exploit attempts. Monitor database logs for unusual queries or access patterns. Restrict network access to the administration interface to trusted IPs only. Conduct regular security assessments and penetration tests focusing on injection flaws. Finally, ensure incident response plans are updated to handle potential data breaches stemming from this vulnerability.

Description

CVE-2025-14207 is a medium severity SQL injection vulnerability in the tushar-2223 Hotel-Management-System, specifically in the /admin/invoiceprint.php file where the ID parameter is improperly sanitized. The vulnerability allows remote attackers to execute arbitrary SQL commands without authentication or user interaction. Exploitation can lead to partial compromise of confidentiality, integrity, and availability of the backend database. The product uses a rolling release model, so specific version details for patched releases are unavailable. Although no known exploits are currently observed in the wild, public exploit code exists, increasing risk. European organizations using this hotel management system should prioritize mitigation to prevent data breaches or service disruptions. Countries with significant hospitality sectors and adoption of this software are at higher risk. Mitigation requires immediate input validation, parameterized queries, and monitoring for suspicious database activity.

Impact

For European organizations, especially those in the hospitality sector using the tushar-2223 Hotel-Management-System, this vulnerability poses a risk of unauthorized data access and manipulation. Confidential customer information such as personal details and payment data could be exposed, leading to privacy violations and regulatory penalties under GDPR. Integrity of booking and billing data could be compromised, causing operational disruptions and financial losses. Availability of the system might also be affected if attackers execute destructive SQL commands. The remote, unauthenticated nature of the exploit increases the attack surface, making it easier for cybercriminals to target multiple organizations. Given the hospitality industry's importance in countries like Spain, Italy, France, and Germany, the impact could be significant, affecting customer trust and business continuity.

Summary

CVE-2025-14207 identifies a SQL injection vulnerability in the tushar-2223 Hotel-Management-System, a software solution used for managing hotel operations. The flaw resides in the /admin/invoiceprint.php script, where the 'ID' parameter is not properly sanitized or validated before being incorporated into SQL queries. This improper handling allows an unauthenticated remote attacker to inject malicious SQL code, potentially manipulating the backend database. The vulnerability is exploitable over the network without requiring any privileges or user interaction, making it highly accessible to attackers. The CVSS 4.0 base score of 6.9 reflects a medium severity, considering the ease of exploitation and the limited but significant impact on confidentiality, integrity, and availability. The product follows a rolling release model, complicating patch tracking as no fixed version numbers are assigned to affected or fixed releases. Although no active exploitation has been reported, publicly available exploit code increases the likelihood of future attacks. The vulnerability could enable attackers to extract sensitive customer data, alter booking records, or disrupt hotel operations, posing a serious risk to organizations relying on this system.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 15 Dec 2025, 05:00 UTC

Technical details

References

Community reviews

Related threats