dbcve.org
InjectionWeakness · CWE-74

CVE-2026-4966

MEDIUM · 6.3 CVSS v3.1 Published 2026-03-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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. Impacted is an unknown function of the file /admin/mod_room/index.php?view=edit. Executing a manipulation of the argument ID can lead to sql injection. The attack can be launched 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 · moderate confidence

The itsourcecode Free Hotel Reservation System 1.0 contains a SQL injection vulnerability in the /admin/mod_room/index.php?view=edit page. The ID parameter is not properly sanitized before being used in database queries, allowing remote attackers to inject arbitrary SQL commands.

MitigationImplement parameterized queries or prepared statements for all database operations involving the ID parameter in the edit room functionality. Validate and sanitize all user inputs before database queries.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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 the itsourcecode Free Hotel Reservation System is installed
    Search the webroot for files from this application, particularly looking for the /admin/ directory structure or any PHP files containing 'hotel' or 'reservation' in the path
    Affected if The application is found in the webroot and the version is 1.0 or cannot be determined to be a later version
  2. Verify the vulnerable file exists
    Check for the presence of /admin/mod_room/index.php in the web directory
    Affected if The file /admin/mod_room/index.php exists in the webroot
  3. Check if the edit functionality is accessible
    Access the URL pattern /admin/mod_room/index.php?view=edit and verify the page loads
    Affected if The edit room page loads without access restrictions
  4. Inspect the ID parameter handling in the edit page
    Examine the source code of /admin/mod_room/index.php and search for SQL queries that use the 'id' parameter without prepared statements or sanitization functions like mysqli_real_escape_string, PDO::prepare, or htmlspecialchars
    Affected if The code contains SQL queries that directly use the 'id' request parameter without parameterized queries or input sanitization

If the Free Hotel Reservation System 1.0 is installed with the /admin/mod_room/index.php file accessible and the code directly uses the 'id' parameter in SQL queries without prepared statements, the environment is affected by this SQL injection vulnerability.

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 or prepared statements for all database operations involving the ID parameter in the edit room functionality. Validate and sanitize all user inputs before database queries.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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