/

CVE-2026-10290

Severity:

HIGH RISK

(7.3)

SQL Injection in Hotel and Tourism Reservation System

CVE-2026-10290

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Database Compromise and Data Exposure

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Hotel and Tourism Reservation System 1.0 contains a SQL injection flaw in tour.php where the GET parameter tour is used unsafely in database queries.

A remote attacker can manipulate this parameter to inject SQL, potentially accessing or altering reservation data and application state.

Affected context

This vulnerability occurs in the tour handling functionality of tour.php within the Hotel and Tourism Reservation System 1.0.

It is present when user-supplied input from the tour GET parameter is incorporated into SQL statements without proper parameterization or encoding.

The issue is most relevant on internet-exposed or shared-hosting deployments where attackers can freely send crafted HTTP requests to the application.

Exploit preconditions

  • Attack surface: HTTP interface handling requests to tour.php
  • Required access: Network access to the web application; no prior authentication is necessarily required if the vulnerable endpoint is public
  • Trigger point: Supplying a crafted value in the tour GET parameter when requesting tour.php
  • Why exploitation is possible: The application appears to concatenate or interpolate the tour parameter directly into SQL queries without using prepared statements or robust input validation, allowing attacker-controlled SQL fragments to alter query logic.

Why this happens

The underlying issue is the direct use of untrusted input in SQL commands, aligning with CWE-89: Improper Neutralization of Special Elements used in an SQL Command.

Instead of using parameterized queries or a safe database abstraction layer, the code likely builds query strings by concatenating the tour parameter, trusting the input to be syntactically benign.

Additionally, the broader class CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component is implicated because unsanitized data is passed into the database engine, a downstream interpreter that executes the injected SQL.

This insecure pattern allows attacker-controlled characters such as quotes, operators, and comment markers to break out of intended constraints and execute arbitrary query logic.

Potential impact

  • May allow retrieval of sensitive customer and reservation data from the database.
  • Could enable modification or deletion of booking records and related business data.
  • Might permit creation of new administrative or privileged application accounts if authentication data is stored in the same database.
  • Can be combined with other weaknesses to attempt authentication bypass or privilege escalation.
  • In some configurations, could lead to full database server compromise through stacked queries or database-specific extensions.

General mitigation guidance

Effective mitigation focuses on treating all external inputs as untrusted and separating data from query logic.

Recommended defensive patterns include:

  • Using parameterized queries / prepared statements with bound parameters for all database operations, including the tour parameter.
  • Employing an ORM or database abstraction that enforces query parameterization by default and discourages string-concatenated SQL.
  • Applying strict server-side validation and normalization of input fields such as tour, restricting them to expected formats (e.g., numeric IDs or whitelisted codes).
  • Centralizing database access logic so that security checks and safe query-building patterns are consistently applied.
  • Running the database with least-privilege accounts, limiting the impact of a successful injection (e.g., read-only where feasible for query-only endpoints).

How teams detect issues like this

Detection generally involves both code-centric and runtime approaches:

  • Static analysis to identify instances where request parameters (e.g., $_GET["tour"] or equivalent) are concatenated or interpolated into SQL strings.
  • Code review checklists that flag any dynamic SQL built from raw HTTP input, especially within files like tour.php that directly handle GET parameters.
  • Use of application security testing tools (SAST/DAST) configured with rules for SQL injection to automatically probe endpoints and verify whether injected payloads alter responses.
  • Logging and monitoring for anomalous query patterns, such as unexpected use of SQL control characters, logic operators, or comment syntax originating from the tour parameter.
  • Security-focused CI/CD gates that block deployments when new unparameterized SQL patterns are introduced.

Sources

SourceLink
code-projects.orgcode-projects.org/
github.comgithub.com/Xmyronn/Hotel-and-Tourism-Reservation-System---Unauthenticated-SQL-Injection.git
vuldb.comvuldb.com/cve/CVE-2026-10290
vuldb.comvuldb.com/submit/825939
vuldb.comvuldb.com/vuln/367583
vuldb.comvuldb.com/vuln/367583/cti

Frequently asked

questions

Yes. An attacker can exploit this issue remotely by sending crafted HTTP requests to the vulnerable tour.php endpoint, provided it is reachable over the network.

Typically only network access to the web application is required. If the vulnerable endpoint does not require authentication, exploitation can occur without valid user credentials.

The most robust fix is to refactor all affected queries to use parameterized statements or an ORM that enforces parameter binding, ensuring that the tour parameter is always treated as data rather than executable SQL.

Establish secure coding standards that prohibit string-concatenated SQL, adopt frameworks that default to prepared statements, enforce input validation for all external parameters, and integrate automated security testing into the development pipeline to catch injection patterns early.

Find out what's already
exploitable in your codebase.