HIGH 7.3

CVE-2026-14755: SQL Injection in Hotel and Tourism Reservation 1.0 Admin Panel

A SQL injection vulnerability exists in code-projects Hotel and Tourism Reservation system version 1.0. The flaw is located in the reservations management page at /admin/reservations.php, where user input passed through the 'delete' parameter is not properly validated before being used in database queries. An unauthenticated attacker on the network can exploit this remotely to read, modify, or delete sensitive reservation data and potentially gain deeper access to the system. Public disclosure means defensive awareness is urgent.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.3 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Weaknesses (CWE)
CWE-74, CWE-89
Affected products
0 configuration(s)
Published / Modified
2026-07-05 / 2026-07-06

NVD description (verbatim)

A vulnerability has been found in code-projects Hotel and Tourism Reservation 1.0. Affected by this vulnerability is an unknown functionality of the file /admin/reservations.php of the component Reservations Management Page. The manipulation of the argument delete leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

6 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-14755 is a SQL injection vulnerability (CWE-74, CWE-89) in code-projects Hotel and Tourism Reservation 1.0. The Reservations Management Page component fails to sanitize the 'delete' parameter in /admin/reservations.php before constructing SQL statements. This allows an attacker to inject arbitrary SQL commands. The vulnerability requires no authentication or user interaction and is accessible over the network, resulting in a CVSS 3.1 score of 7.3 (HIGH). The public disclosure means exploitation proof-of-concept material is available.

Business impact

This vulnerability poses significant risk to hospitality businesses relying on this reservation system. Attackers can exfiltrate guest personal data (names, contact information, payment details), modify or delete reservations to disrupt operations, or establish a foothold for lateral movement within the network. For organizations using Hotel and Tourism Reservation 1.0, immediate remediation is essential to avoid data breach liability, operational disruption, and reputational harm.

Affected systems

code-projects Hotel and Tourism Reservation version 1.0 is affected. Any instance exposed to network traffic—particularly internet-facing administrative interfaces—is at risk. Check your inventory for this product and version combination. Cloud and on-premises deployments are both in scope.

Exploitability

Exploitability is high. The attack requires no authentication, no user interaction, and no special network positioning. A remote attacker can craft malicious SQL queries through the 'delete' parameter and execute them immediately. Because the vulnerability has been disclosed publicly, active exploit attempts are a realistic concern. Automated scanning and opportunistic attacks are likely.

Remediation

Upgrade code-projects Hotel and Tourism Reservation to a patched version released by the vendor; consult the official vendor advisory for the specific build number. If an immediate patch is unavailable, apply input validation and parameterized query techniques to the affected /admin/reservations.php file. Consider restricting administrative interface access via network-level controls (IP allowlisting, VPN requirement) and monitor database activity for anomalous queries.

Patch guidance

Contact code-projects for the official patch release addressing SQL injection in the delete parameter. Verify patch availability and compatibility with your deployment before applying. Test in a non-production environment first. If the vendor has not yet released a patch, document your remediation approach (code-level fixes or compensating controls) and escalate to your vendor relationship manager.

Detection guidance

Monitor web server access logs and database audit logs for suspicious patterns in /admin/reservations.php requests, particularly those containing SQL keywords or special characters in the 'delete' parameter (e.g., single quotes, UNION, SELECT, OR). Deploy WAF rules to block common SQL injection payloads. Enable query logging on your database to catch unauthorized or malformed SQL attempts. Consider implementing intrusion detection signatures specific to this CVE once they become available.

Why prioritize this

This vulnerability warrants immediate attention because (1) it is unauthenticated and remotely exploitable with no user interaction required, (2) it offers direct database access, (3) public disclosure increases attack likelihood, and (4) it affects critical business data—guest and reservation information. Organizations running version 1.0 should treat remediation as urgent priority.

Risk score, explained

The CVSS 3.1 score of 7.3 (HIGH) reflects a network-accessible, unauthenticated attack with low complexity and direct impact on confidentiality, integrity, and availability. While not critical, the combination of ease of exploitation, lack of privilege requirements, and real-world availability of exploit details justifies elevated urgency in your patch cycle.

Frequently asked questions

Does this vulnerability require authentication to exploit?

No. The vulnerability can be exploited by any unauthenticated attacker with network access to the affected /admin/reservations.php endpoint. This is one of the factors making it high-risk.

What data is at risk if my system is compromised?

Guest personal information (names, email addresses, phone numbers), reservation details, and potentially payment information stored in the reservation system database. Attackers may also pivot to other systems if the database server has elevated network privileges.

Are there any temporary workarounds if I cannot patch immediately?

Restrict network access to /admin/reservations.php using a firewall or reverse proxy (IP allowlisting, VPN requirement), disable the feature if operationally feasible, and implement detailed logging to detect exploitation attempts. These are not substitutes for patching but can reduce exposure.

How do I verify if my system has been compromised?

Review database audit logs and web server access logs for unusual SQL queries or requests to /admin/reservations.php with suspicious parameters. Look for entries containing SQL keywords, comment characters (--), or unusual character encoding. Also check for unexpected database users or privilege changes.

This analysis is provided for informational and defensive purposes only. It does not constitute legal or compliance advice. Organizations should validate all remediation steps against their specific deployment, vendor guidance, and internal security policies. SEC.co does not provide vulnerability scores or KEV status independently; all technical data herein derives from authoritative sources including the vendor advisory and CVSS official calculator. Test all patches and mitigations in non-production environments before production deployment. Source: NVD (public-domain), retrieved 2026-08-14. Analysis generated by SEC.co (claude-haiku-4-5).