CVE-2026-14717
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 · uneditedA vulnerability was detected in itsourcecode Hospital Management System 1.0. The affected element is an unknown function of the file /patientlogin.php. Performing a manipulation of the argument loginid results in sql injection. Remote exploitation of the attack is possible. The exploit is now 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 · moderate confidenceSQL injection vulnerability in the patient login functionality of itsourcecode Hospital Management System 1.0. The loginid parameter in /patientlogin.php is not properly sanitized, allowing attackers to inject malicious SQL queries through the argument.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Hospital Management System installationLocate the itsourcecode Hospital Management System installation directory and identify if version 1.0 is deployed. Check for patientlogin.php in the web root or application directory.Affected if The system is itsourcecode Hospital Management System version 1.0 with patientlogin.php present
-
Locate patientlogin.phpNavigate to the web server document root and find /patientlogin.php file. Verify it exists and is accessible via HTTP/HTTPS.Affected if The patientlogin.php file exists and is publicly accessible
-
Inspect loginid parameter handlingOpen patientlogin.php and search for code handling the 'loginid' POST or GET parameter. Examine how this parameter is used in SQL queries.Affected if The loginid parameter is directly concatenated into SQL queries without sanitization or prepared statements
-
Check for parameterized queriesReview the database query code in patientlogin.php for use of prepared statements, parameterized queries, or input validation functions (such as mysqli_prepare, PDO::prepare, or escaping functions).Affected if No parameterized queries or input validation is used for the loginid parameter in SQL statements
-
Test for SQL injection vulnerabilityUsing a safe testing methodology, submit a single quote (') or common SQL injection payloads (e.g., ' OR '1'='1) in the loginid field and observe if SQL error messages are returned or if the application behaves unexpectedly.Affected if SQL injection payloads produce database errors or alter application behavior
You are affected if you run itsourcecode Hospital Management System 1.0 with accessible patientlogin.php where the loginid parameter is used in unsanitized dynamic SQL queries.
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 dynamic SQL queries with parameterized queries/prepared statements for the loginid parameter. Implement strict input validation and consider deploying a WAF as an additional layer of defense.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14717 — 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-14717 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