CVE-2026-5551
Received Received - Intake
SQL Injection in itsourcecode Free Hotel Reservation System Admin Login

Publication date: 2026-04-05

Last updated on: 2026-04-29

Assigner: VulDB

Description
A security flaw has been discovered in itsourcecode Free Hotel Reservation System 1.0. This vulnerability affects unknown code of the file /hotel/admin/login.php of the component Parameter Handler. The manipulation of the argument email results in sql injection. The attack may be launched remotely. The exploit has been released to the public and may be used for attacks.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-05
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2026-04-05
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
itsourcecode free_hotel_reservation_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-74 The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-5551 is a critical SQL injection vulnerability found in the Free Hotel Reservation System version 1.0, specifically in the /hotel/admin/login.php file. The flaw arises because the 'email' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without any authentication.

Attackers can exploit this vulnerability using various SQL injection techniques such as boolean-based blind, error-based, stacked queries, and time-based blind SQL injection to gain unauthorized access to the database, leak or tamper data, take full control of the system, or disrupt services.


How can this vulnerability impact me? :

This vulnerability can have severe impacts including unauthorized access to sensitive data, data leakage, and data tampering. Attackers may gain full control over the affected system, potentially leading to service disruption and loss of business continuity.

  • Unauthorized database access
  • Data leakage and tampering
  • Full system compromise
  • Potential service disruption

How can this vulnerability be detected on my network or system? Can you suggest some commands?

The CVE-2026-5551 vulnerability can be detected by testing the 'email' parameter in the /hotel/admin/login.php file for SQL injection flaws.

Example payloads to test include boolean-based blind, error-based, stacked queries, and time-based blind SQL injection techniques.

  • Boolean-based blind: email=admin@123' RLIKE (SELECT (CASE WHEN (6011=6011) THEN 0x61646d696e40313233 ELSE 0x28 END))--
  • Error-based: email=admin@123' AND (SELECT 1627 FROM(SELECT COUNT(*),CONCAT(0x7178626a71,(SELECT (ELT(1627=1627,1))),0x7171706271,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)--
  • Stacked queries: email=admin@123';SELECT SLEEP(5) #
  • Time-based blind: email=admin@123' AND (SELECT 1479 FROM (SELECT(SLEEP(5)))UySv)--

Testing can be automated using tools like sqlmap to confirm the presence of the vulnerability.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps for CVE-2026-5551 include:

  • Use prepared statements with parameter binding to separate SQL code from user input.
  • Implement strict input validation and filtering to ensure inputs conform to expected formats.
  • Minimize database user permissions by avoiding high-privilege accounts for routine operations.
  • Conduct regular security audits to detect and fix vulnerabilities promptly.

How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The CVE-2026-5551 vulnerability is a critical SQL injection flaw that allows unauthorized database access, data leakage, and data tampering. Such security weaknesses can lead to exposure of sensitive personal or health information, which directly impacts compliance with regulations like GDPR and HIPAA that mandate protection of personal data and patient health information.

Failure to address this vulnerability may result in unauthorized disclosure or alteration of protected data, violating confidentiality, integrity, and availability requirements imposed by these standards. This can lead to legal penalties, loss of trust, and damage to business continuity.

Therefore, organizations using the affected system must remediate the vulnerability promptly by implementing recommended security measures such as prepared statements, input validation, and least privilege database access to maintain compliance with common data protection regulations.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart