CVE-2026-54419
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 · uneditedclaudiopizzillo PIAF-HMS (PBX-In-A-Flash Hotel Management System; no released versions, latest commit 389d2633441b65ced1c104212cd62be2bfca21e5) contains multiple unauthenticated SQL injection vulnerabilities. The application has no authentication mechanism and passes user-supplied HTTP parameters directly into deprecated mysql_query calls via string concatenation, without sanitization, escaping, or parameterization.
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 confidencePIA F-HMS hotel management system contains unauthenticated SQL injection vulnerabilities across multiple PHP files (rooms.php, checkuser.php, ec.php, checkin.php, wakeup.php, bills.php, rates.php, checkout.php). User-supplied HTTP GET/POST parameters are concatenated directly into deprecated mysql_query() calls without sanitization, escaping, or parameterization, allowing remote attackers to inject arbitrary SQL commands.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify PIA F-HMS installationLocate the hotel management system web directory and search for the known vulnerable PHP files: rooms.php, checkuser.php, ec.php, checkin.php, wakeup.php, bills.php, rates.php, checkout.phpAffected if Any of these files exist in the web application directory
-
Verify deprecated mysql_query usageOpen each vulnerable PHP file and search for the string 'mysql_query' - the vulnerability stems from use of this deprecated functionAffected if The code contains mysql_query() calls, indicating the vulnerable code pattern exists
-
Check for unauthenticated accessConfirm the vulnerable PHP files are accessible without authentication - the SQL injection is exploitable without login credentialsAffected if The application does not require authentication to access the affected PHP endpoints
-
Inspect parameter handlingReview the PHP source code for direct concatenation of $_GET or $_POST parameters into SQL queries (e.g., $_GET['param'] directly in query string)Affected if HTTP parameters are concatenated directly into SQL queries without sanitization or parameter binding
-
Confirm application is exposedVerify the web server serves the PIA F-HMS application endpoints over HTTP/HTTPS - the attack vector is remote via web requestsAffected if The hotel management system is accessible over the network
A user is affected if PIA F-HMS is installed with any of the vulnerable PHP files present and the deprecated mysql_query() pattern with unsanitized parameter concatenation is in use.
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 all mysql_query() calls with prepared statements using PDO or mysqli, implement proper input validation, and add authentication. The application requires fundamental architecture changes to remediate these critical vulnerabilities.
- Consultation8.0 h
- Implementation40.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $20,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54419 — 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-54419 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