CVE-2026-14638
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 flaw has been found in itsourcecode Hospital Management System 1.0. This affects an unknown function of the file /patient.php. This manipulation of the argument editid causes sql injection. The attack may be initiated 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 · high confidenceThe itsourcecode Hospital Management System 1.0 is vulnerable to SQL injection via the editid parameter in the /patient.php file. An attacker can inject malicious SQL queries through this parameter to manipulate database operations, potentially exfiltrating sensitive patient data, modifying records, or compromising the entire database.
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 patient.php file within the web application directory structure. Common paths include /patient.php or /admin/patient.php at the web root.Affected if The patient.php file exists in the application and is accessible via HTTP requests.
-
Verify application versionCheck if the installed version is itsourcecode Hospital Management System 1.0. Review any version disclosure files, footer text, or meta tags within the application.Affected if The application is itsourcecode Hospital Management System version 1.0.
-
Inspect the editid parameter handlingExamine the patient.php file source code to locate the code handling the editid parameter. Search for SQL queries that incorporate this parameter without using prepared statements or parameterized queries.Affected if The editid parameter is used in SQL queries without parameterized binding, allowing arbitrary SQL manipulation.
-
Test the parameter for SQL injectionSend a crafted HTTP request to patient.php with the editid parameter set to a SQL injection payload (e.g., editid=1' OR '1'='1) and observe the database response or error messages.Affected if The application returns database errors, unexpected data, or behaves differently based on the SQL injection payload, indicating unsanitized input acceptance.
The system is affected if it runs itsourcecode Hospital Management System 1.0 with the patient.php file accessible and the editid parameter handling vulnerable to SQL injection.
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 dataImplement prepared statements/parameterized queries for all database operations in patient.php, particularly for the editid parameter. Validate and sanitize all user inputs, and apply the principle of least privilege to database accounts.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14638 — 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-14638 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