InjectionWeakness · CWE-74

CVE-2026-4237

HIGH · 7.3 CVSS v3.1 Published 2026-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 flaw has been found in itsourcecode Free Hotel Reservation System 1.0. This vulnerability affects unknown code of the file /hotel/admin/mod_reports/index.php. Executing a manipulation of the argument Home can lead to sql injection. The attack may be performed from remote. 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 · moderate confidence

SQL injection vulnerability in itsourcecode Free Hotel Reservation System 1.0 allows remote attackers to inject malicious SQL queries via the 'Home' parameter in the file /hotel/admin/mod_reports/index.php. The vulnerability has a CVSS score of 7.3 (HIGH).

MitigationImplement parameterized queries (prepared statements) for all database operations in the affected file and add proper input validation/sanitization for the Home parameter. Restrict admin panel access to authorized users only as an additional defense layer.

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 checks

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

  1. Confirm product and version
    Identify if the deployed application is itsourcecode Free Hotel Reservation System version 1.0. Check application files, headers, or version documentation for the exact version number.
    Affected if The installed version is itsourcecode Free Hotel Reservation System 1.0 and matches the affected release.
  2. Locate the affected PHP file
    Verify the existence of the file /hotel/admin/mod_reports/index.php in the web root directory. Inspect the file contents to confirm it processes the 'Home' parameter.
    Affected if The file /hotel/admin/mod_reports/index.php exists and contains code that handles the 'Home' parameter without proper sanitization.
  3. Inspect parameter handling in the code
    Review the source code of /hotel/admin/mod_reports/index.php and search for the 'Home' parameter usage. Determine if it is directly interpolated into SQL queries without prepared statements or input validation.
    Affected if The 'Home' parameter is concatenated into SQL queries without parameterized queries or escaping.
  4. Check application accessibility
    Determine if the /hotel/admin/ path is accessible over the network and if authentication is required. Attempt to access the mod_reports module.
    Affected if The admin panel and mod_reports module are accessible without proper authentication or the 'Home' parameter can be submitted via HTTP requests.

A user is affected if they are running itsourcecode Free Hotel Reservation System version 1.0, the file /hotel/admin/mod_reports/index.php exists, and the 'Home' parameter in that file is processed without SQL injection protection.

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

Implement parameterized queries (prepared statements) for all database operations in the affected file and add proper input validation/sanitization for the Home parameter. Restrict admin panel access to authorized users only as an additional defense layer.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4237 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4237 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