CVE-2026-14763
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA flaw has been found in code-projects Hotel and Tourism Reservation 1.0. This affects an unknown function of the file /admin/tour_reserves.php of the component Tour Reservations Page. This manipulation of the argument tour causes sql injection. The attack can be initiated remotely. The exploit has been published and may be used.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in the Tour Reservations page of code-projects Hotel and Tourism Reservation 1.0. The 'tour' parameter in /admin/tour_reserves.php is not properly sanitized, allowing attackers to inject malicious SQL queries. The vulnerability is remotely exploitable and has a CVSS score of 7.3 (HIGH).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Hotel and Tourism Reservation versionLocate the application source code and check for version identifiers in header files, README files, or configuration files. Common locations include version.php, about.php, or the main index file.Affected if The application version is 1.0 and is the code-projects variant.
-
Verify the vulnerable file existsCheck if /admin/tour_reserves.php exists in the web root or application directory. This file is part of the admin panel for the Hotel and Tourism Reservation system.Affected if The file /admin/tour_reserves.php is present in the installation.
-
Inspect the tour_reserves.php source code for SQL injection vulnerabilityOpen /admin/tour_reserves.php and search for SQL query patterns that use the 'tour' parameter without sanitization. Look for direct insertion of $_GET['tour'], $_POST['tour'], or similar user input into SQL statements without prepared statements, parameterized queries, or escaping functions.Affected if The code contains SQL queries that incorporate the 'tour' parameter directly from user input without sanitization or parameterized queries.
-
Check if the application accepts user input to the tour parameterTest if the /admin/tour_reserves.php endpoint processes a 'tour' parameter via GET or POST request. Attempt a normal request with a tour parameter value and verify the application processes it.Affected if The application accepts and processes a 'tour' parameter in requests to tour_reserves.php.
The environment is affected if Hotel and Tourism Reservation 1.0 is installed, the file /admin/tour_reserves.php exists, and that file contains SQL queries using the 'tour' parameter directly from user input without sanitization or prepared statements.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace dynamic SQL queries with parameterized queries/prepared statements in tour_reserves.php, and implement proper input validation for the 'tour' parameter. If possible, apply the vendor patch or upgrade to a secure version.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14763 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-14763 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data