dbcve.org
Simple Online Hotel Reservation SystemApplication · Fabian

CVE-2025-6450

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability was found in code-projects Simple Online Hotel Reservation System 1.0. It has been classified as critical. This affects an unknown part of the file /admin/confirm_reserve.php. The manipulation of the argument transaction_id leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public 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 confidence

SQL injection vulnerability in Simple Online Hotel Reservation System 1.0 allows remote attackers to inject malicious SQL commands via the transaction_id parameter in /admin/confirm_reserve.php. The lack of input sanitization or parameterized queries enables database compromise.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries and implement strict input validation on all user-supplied parameters before database operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Simple Online Hotel Reservation SystemApplication
Affected:= 1.0

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify the Simple Online Hotel Reservation System is installed
    Locate the application on your web server. Common paths include /var/www/html/ or C:\inetpub\wwwroot\. Look for directories containing hotel, reservation, or the application's source files.
    Affected if The Fabian Simple Online Hotel Reservation System version 1.0 is present on the server.
  2. Confirm the vulnerable file exists
    Check if the file /admin/confirm_reserve.php exists in the web application directory. Navigate to the application root and look for the confirm_reserve.php file within an admin subdirectory.
    Affected if The file /admin/confirm_reserve.php exists in the application installation.
  3. Check if the admin interface is web-accessible
    Attempt to access the /admin/ directory or confirm_reserve.php via HTTP/HTTPS from a browser or curl command. For example: curl -I http://TARGET/admin/confirm_reserve.php
    Affected if The /admin/confirm_reserve.php endpoint is reachable over the network without authentication restrictions.
  4. Identify the installed version
    Review any version.php, readme.txt, or changelog file in the application root directory. Alternatively, check the source code of confirm_reserve.php for version comments or the application's footer for version display.
    Affected if The installed version is exactly 1.0 as indicated in the affected products.
  5. Verify the transaction_id parameter is handled without prepared statements
    Open /admin/confirm_reserve.php in a text editor and search for the transaction_id parameter usage. Look for SQL queries that concatenate or embed this parameter directly without using prepare() or parameterized queries.
    Affected if The code directly uses the transaction_id parameter in SQL queries without input sanitization or prepared statements.

You are affected if the Simple Online Hotel Reservation System version 1.0 is installed with the /admin/confirm_reserve.php file accessible and the transaction_id parameter processed without prepared statements.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with prepared statements/parameterized queries and implement strict input validation on all user-supplied parameters before database operations.

Fix this in Simple Online Hotel Reservation System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6450 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-6450 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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