/

CVE-2026-13555

Severity:

HIGH RISK

(7.3)

SQL Injection (CWE-89) in Hotel Admin User Creation

CVE-2026-13555

Deferred

Vulnerability type

Category:

SQL Injection

CWE:

CWE-74, CWE-89

Impact:

Database Compromise and Authentication Bypass

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

An SQL injection flaw in the Online Hotel Management System 1.0 allows attacker-controlled data in the Name parameter to be embedded directly into backend SQL queries.

When an unauthenticated or low-privileged user can reach the admin user creation endpoint, this issue can enable data access, modification, or account compromise in the hotel management database.

Affected context

The vulnerability occurs in the Online Hotel Management System 1.0 within the administrative user management module, specifically at /admin/mod_users/controller.php?action=add.

It manifests when the Name parameter is taken from HTTP requests and used in database operations without adequate sanitization, encoding, or prepared statements.

Any deployment exposing this endpoint over a network where attackers can send crafted HTTP requests may be affected, depending on access control around the admin interface.

Exploit preconditions

  • Attack surface: HTTP interface of the Online Hotel Management System, targeting the /admin/mod_users/controller.php?action=add endpoint.
  • Required access: Ability to send requests to the admin user management path; this may be unauthenticated or weakly protected in some deployments.
  • Trigger point: Submission of a crafted Name parameter value during user creation or modification.
  • Why exploitation is possible: The Name argument is concatenated directly into SQL statements without parameterization or proper output encoding, allowing attackers to alter query structure.

Why this happens

The root cause aligns with CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') and is related to CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component.

The application constructs SQL queries dynamically by embedding the Name parameter directly into the query string, treating user-controlled input as trusted.

Without prepared statements, strict input validation, or context-aware encoding, special characters in the Name parameter can break out of the intended data context and modify the SQL logic executed by the database.

Potential impact

  • Attackers may read, modify, or delete hotel booking, customer, and user account records.
  • Malicious users could create or escalate administrative accounts, leading to full application takeover.
  • The database integrity can be compromised through injected data or mass updates.
  • Under certain configurations, attackers may leverage SQL injection to execute database-level functions that further expand access.

General mitigation guidance

Effective mitigation generally focuses on eliminating dynamic SQL construction with raw user input and reducing trust in external data:

  • Use parameterized queries or prepared statements for all database operations involving user-supplied values, including admin modules.
  • Apply strict server-side validation on fields like Name, enforcing expected character sets and length limits consistent with real-world data.
  • Implement context-aware escaping or encoding at the database layer when parameterization is not feasible.
  • Restrict access to administrative endpoints using strong authentication, role-based authorization, and network-level controls.
  • Apply the principle of least privilege to database accounts so that application credentials can perform only necessary operations.

How teams detect issues like this

Organizations can detect SQL injection risks using a combination of code and runtime analysis:

  • Static analysis: Configure rules to flag dynamic SQL built via string concatenation or interpolation with request parameters, especially in admin-related controllers.
  • Code review: Look for database calls that accept raw $_GET, $_POST, or similar inputs without validation, and verify that all queries use parameter binding.
  • Dynamic testing: Run web application security scanners or fuzzers to send crafted input into parameters like Name and observe for SQL errors or anomalous responses.
  • Monitoring and logging: Enable detailed database and application logs to highlight unexpected query patterns, error messages, or spikes in failed queries.

Sources

SourceLink
github.comgithub.com/Hh-176/CVE/issues/6
itsourcecode.comitsourcecode.com/
vuldb.comvuldb.com/cve/CVE-2026-13555
vuldb.comvuldb.com/submit/843585
vuldb.comvuldb.com/vuln/374563
vuldb.comvuldb.com/vuln/374563/cti

Frequently asked

questions

Yes. As long as an attacker can reach the affected admin endpoint over the network and submit requests with a crafted Name parameter, the vulnerability can be exploited remotely.

The required access depends on how the admin interface is exposed. If it is not properly restricted, attackers may not need prior authentication. Where authentication exists, any account able to hit the user creation path could potentially exploit the flaw.

The safest approach is to refactor all affected queries to use parameterized statements or prepared queries and to ensure that user input is never directly concatenated into SQL strings. Combine this with strict validation rules on all input fields.

Adopt a development standard that mandates parameterized queries by default, include secure coding checks in code review, run automated static and dynamic security tests in the CI/CD pipeline, and regularly review admin endpoints for strict access control and input handling.

Find out what's already
exploitable in your codebase.