InjectionWeakness · CWE-74

CVE-2026-4612

HIGH · 7.3 CVSS v3.1 Published 2026-03-23

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

NVD · unedited

A vulnerability has been found in itsourcecode Free Hotel Reservation System 1.0. This affects an unknown part of the file /hotel/admin/mod_users/index.php?view=edit&id=8 of the component Parameter Handler. The manipulation of the argument account_id leads to sql injection. Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used.

Technical summary

dbcve analysis · high confidence

SQL injection vulnerability in itsourcecode Free Hotel Reservation System 1.0 allows remote attackers to inject malicious SQL queries via the account_id parameter in the /hotel/admin/mod_users/index.php file when editing users. The Parameter Handler component fails to properly sanitize user input, enabling database manipulation.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements for the account_id parameter in the affected PHP file. Alternatively, implement strict input validation and output encoding. Restrict admin panel access to trusted networks until a patch is applied.

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

CVSS breakdown

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?

dbcve checks

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

Verify the itsourcecode Free Hotel Reservation System is installed

Locate the web application's root directory and confirm the presence of itsourcecode Free Hotel Reservation System files, typically in a web server document root (e.g., /var/www/html/hotel or C:\inetpub\wwwroot\hotel)

Affected if The application is present and appears to be the itsourcecode Free Hotel Reservation System
Confirm the application version is 1.0

Check for a version file, readme, or any version identifier within the application root. Common locations include a version.php file, readme.txt, or the main index.php header comments

Affected if The installed version is 1.0 (the only version listed as affected)
Verify the affected file exists

Check for the presence of /hotel/admin/mod_users/index.php within the web application directory structure

Affected if The file /hotel/admin/mod_users/index.php exists in the application
Determine if admin panel is accessible

Attempt to access the admin login page at /hotel/admin/ or verify network accessibility to the admin interface. Check web server access logs for requests to this path

Affected if The admin panel is reachable from the network (the SQL injection requires accessing the user editing function in mod_users)
Inspect the account_id parameter handling

Review the source code of /hotel/admin/mod_users/index.php and look for SQL queries that incorporate the account_id parameter without proper sanitization or prepared statements

Affected if The code contains dynamic SQL queries using the account_id parameter without parameterized queries or input sanitization

A user is affected if they have itsourcecode Free Hotel Reservation System version 1.0 installed with the admin panel accessible and the vulnerable /hotel/admin/mod_users/index.php file present containing unsanitized account_id parameter handling in SQL queries.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements for the account_id parameter in the affected PHP file. Alternatively, implement strict input validation and output encoding. Restrict admin panel access to trusted networks until a patch is applied.

Have this fixed Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing3.0 h
Review / QA2.0 h

14.0 hours of engineering $2,490

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-4612?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 7.3 High

Exploit likelihood EPSS, next 30 days 0.3%

Remediation

A high-priority fix

Have this fixed 14 hrs · Moderate

Typical engagement from $2,490

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-4612 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References