HIGH 7.3

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

A SQL injection vulnerability exists in the Hotel and Tourism Reservation system version 1.0, specifically in the room management administrative interface. An attacker can manipulate the 'delete' parameter in the /admin/rooms.php file to execute unauthorized database queries without authentication. This allows remote attackers to read, modify, or delete sensitive data from the reservation system's database. The vulnerability is now public and active exploits are known to exist.

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-07

NVD description (verbatim)

A vulnerability was detected in code-projects Hotel and Tourism Reservation 1.0. The impacted element is an unknown function of the file /admin/rooms.php of the component Room Management Page. The manipulation of the argument delete results in sql injection. It is possible to launch the attack remotely. The exploit is now public and may be used.

6 reference(s) · View on NVD →

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

Technical summary

CVE-2026-14762 is a unauthenticated remote SQL injection vulnerability affecting code-projects Hotel and Tourism Reservation 1.0. The vulnerability exists in the Room Management Page component (/admin/rooms.php) where user-supplied input in the 'delete' parameter is not properly sanitized before being incorporated into SQL queries. The attack requires no authentication, no special configuration, and no user interaction. The vulnerability impacts confidentiality, integrity, and availability of the underlying database through classic SQL injection techniques (CWE-89) enabled by improper input validation (CWE-74).

Business impact

Exploitation of this vulnerability could allow attackers to exfiltrate guest information, reservation records, payment data, and other sensitive business information from the hotel system database. Attackers may also modify or delete reservation data, causing operational disruption and customer service failures. The ability to corrupt data without detection creates compliance risks related to data protection regulations and fraud liability. Hotels using this system face potential reputation damage, guest notification requirements, and regulatory penalties depending on the nature of data compromised.

Affected systems

code-projects Hotel and Tourism Reservation version 1.0 is affected. Organizations running this software should immediately identify all deployed instances, particularly those exposed to network access. The vulnerable component is the administrative interface, meaning systems with exposed /admin/ directories are at higher risk. No vendor patch information is currently available; verify directly with the vendor regarding patch status and timeline.

Exploitability

This vulnerability has a CVSS v3.1 score of 7.3 (HIGH) reflecting the combination of remote exploitability without authentication and direct impact on data confidentiality, integrity, and availability. The attack vector is network-based, the attack complexity is low, and no privileges or user interaction are required. The fact that public exploits now exist significantly increases practical exploitation risk. Attack surface is high for any organization with internet-facing or internal network access to the /admin/rooms.php endpoint.

Remediation

Immediate actions: (1) Identify all instances of Hotel and Tourism Reservation 1.0 in your environment, including test and development systems. (2) Restrict network access to the /admin/ directory using firewall rules, WAF policies, or reverse proxy authentication until a patch is available. (3) Isolate affected systems from internet exposure if operationally feasible. (4) Monitor database activity for suspicious SQL queries. Contact the vendor (code-projects) immediately for patch availability and timelines. If no patch is forthcoming, evaluate alternative hotel management systems. Apply vendor patches immediately upon release.

Patch guidance

No patch version information is currently available from vendor advisories for this vulnerability. Contact code-projects directly to request patch availability and expected release timelines. Do not delay remediation while waiting for a patch; implement access controls and monitoring as interim mitigations. When patches are released, prioritize testing and deployment to affected systems within 24-48 hours given the public exploit availability and HIGH severity rating.

Detection guidance

Monitor /admin/rooms.php access logs for suspicious patterns, particularly requests containing SQL syntax keywords (SELECT, UNION, DROP, DELETE, INSERT) in the 'delete' parameter. Enable database query logging and alert on failed queries, error messages, or unusual query patterns. Web application firewalls should be configured to block or alert on common SQL injection payloads targeting the delete parameter. Review access logs for any successful administrative changes made without corresponding user actions. Monitor for unusual data access patterns, mass deletion events, or data exfiltration from the reservation database.

Why prioritize this

This vulnerability warrants immediate prioritization due to: (1) HIGH CVSS severity (7.3) with unauthenticated remote attack vector, (2) public exploit availability reducing the barrier to attack, (3) direct impact on sensitive guest and business data, (4) lack of authentication requirement, (5) operational impact through potential data corruption. Organizations should treat this as a critical remediation item, particularly if the affected system is internet-accessible or handles production reservation data.

Risk score, explained

The CVSS v3.1 score of 7.3 (HIGH) reflects: Network attack vector (AV:N) with no prerequisites for remote exploitation, Low attack complexity (AC:L) with straightforward SQL injection techniques, No privilege requirements (PR:N) to trigger the vulnerability, No user interaction (UI:N) needed, and Unchanged scope (S:U) with direct impact to the affected system. The vulnerability affects all three security objectives: Confidentiality (read data), Integrity (modify data), and Availability (delete data). The score appropriately reflects the severity of unauthenticated SQL injection in a business-critical system, though organizations should escalate priority further given active public exploitation.

Frequently asked questions

What versions of Hotel and Tourism Reservation are affected?

Version 1.0 is confirmed vulnerable. If you are using this product, verify your version immediately and confirm with the vendor whether any other versions may be affected.

Do I need to be an authenticated admin user to exploit this vulnerability?

No. This is an unauthenticated SQL injection vulnerability, meaning attackers do not need valid credentials to attempt exploitation. The /admin/rooms.php endpoint is accessible to anyone with network access unless additional access controls are in place.

What data is at risk if this vulnerability is exploited?

The database underlying the Hotel and Tourism Reservation system is at risk, including guest personal information, reservation records, payment data, room inventory, and any other data stored in the database. Attackers can read, modify, or delete data depending on database permissions.

How can I protect my system if no patch is available yet?

Implement network access controls to restrict access to the /admin/ directory via firewall rules or WAF policies. Isolate affected systems from internet exposure. Enable database and application logging to detect exploitation attempts. Contact the vendor for patch status. Consider evaluating alternative reservation systems if the vendor does not provide timely security updates.

This analysis is provided for informational purposes to assist security teams in vulnerability assessment and remediation planning. No exploit code or weaponized proof-of-concept is provided. Organizations must independently verify all vulnerability details against official vendor advisories before taking remediation actions. Patch version numbers, KEV status, and affected product lists should be verified directly with code-projects and the National Vulnerability Database. This assessment does not constitute legal advice regarding compliance obligations. Organizations are responsible for evaluating the applicability of this vulnerability to their specific environment and business context. Source: NVD (public-domain), retrieved 2026-08-14. Analysis generated by SEC.co (claude-haiku-4-5).