VulnerabilityPublished 16 Feb 2026Updated 23 Feb 2026

CVE-2026-2553: tushar-2223 Hotel-Management-System · SQL Injection

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

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 14:05 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 12% 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 16 Feb 2026
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

Affected software

Product	Affected	Fixed in
tushar-2223Hotel-Management-System	Affected =bb1f3b3666124b888f1e4bcf51b6fba9fbb01d15	Fixed in–

AI-suggested

Given the absence of official patches or vendor response, organizations should immediately implement input validation and sanitization controls at the web application firewall (WAF) or reverse proxy level to block malicious SQL payloads targeting the Name and Email parameters. Employ parameterized queries or prepared statements in any custom integrations or extensions to the system if possible. Conduct thorough code reviews and penetration testing focused on input handling in /home.php and related components. Monitor database and application logs for unusual query patterns or errors indicative of SQL injection attempts. Restrict database user privileges to the minimum necessary to limit the impact of potential exploitation. Consider isolating the affected system within segmented network zones to reduce exposure. If feasible, migrate to alternative hotel management solutions with active vendor support. Maintain regular backups of critical data to enable recovery from potential data corruption or deletion. Stay alert for any future vendor updates or community patches addressing this vulnerability.

Description

A security flaw has been discovered in tushar-2223 Hotel-Management-System up to bb1f3b3666124b888f1e4bcf51b6fba9fbb01d15. This affects an unknown part of the file /home.php of the component HTTP POST Request Handler. Performing a manipulation of the argument Name/Email results in sql injection. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The SQL injection vulnerability allows attackers to execute arbitrary SQL commands on the backend database, potentially leading to unauthorized disclosure of sensitive customer and business data, unauthorized modification or deletion of records, and disruption of hotel management services. This can result in data breaches affecting customer privacy, financial losses, reputational damage, and regulatory non-compliance for organizations using the affected system. Since the attack requires no authentication and can be launched remotely, the attack surface is broad, increasing the risk of widespread exploitation. The continuous delivery model without clear versioning complicates patch management, potentially prolonging exposure. Organizations may face operational disruptions if attackers leverage the vulnerability to corrupt or delete critical data. The public availability of exploit code further elevates the threat level by enabling less skilled attackers to exploit the flaw.

Summary

CVE-2026-2553 identifies a SQL injection vulnerability in the tushar-2223 Hotel-Management-System, specifically within the /home.php file's HTTP POST request handler. The vulnerability arises from improper sanitization or validation of user-supplied input in the Name and Email parameters, allowing attackers to inject malicious SQL queries. Exploitation requires no authentication or user interaction and can be performed remotely, making it accessible to a wide range of threat actors. The affected product employs continuous delivery with rolling releases, complicating precise version identification and patch management. The vendor has not issued any response or patch, and no official fixes are currently available. The CVSS 4.0 base score is 5.3 (medium), reflecting the moderate impact and ease of exploitation without privileges. Public exploit code has been released, increasing the likelihood of attacks. The vulnerability can compromise confidentiality by exposing sensitive data, integrity by altering database contents, and availability by potentially disrupting service. The lack of vendor response and patch availability increases the urgency for organizations to implement compensating controls.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:21 UTC

Technical details

References

Community reviews

Related threats