CVE-2026-14773
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 found in itsourcecode Hospital Management System 1.0. This affects an unknown function of the file /payment.php. The manipulation of the argument patientid results in sql injection. The attack can be launched remotely. The exploit has been made public and could 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 patientid parameter of /payment.php in itsourcecode Hospital Management System 1.0, allowing remote attackers to inject malicious SQL queries through user input that is not properly sanitized or parameterized.
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 web application root directory and verify the presence of itsourcecode Hospital Management System files, specifically checking for payment.php in the web-accessible pathAffected if The application is itsourcecode Hospital Management System version 1.0 and contains payment.php in the web directory
-
Identify database connectivityCheck if the application is configured with a database connection by examining configuration files (such as db.php, config.php, or similar) in the application rootAffected if The application connects to a database, as SQL injection requires an active database connection to be exploitable
-
Locate patientid parameter handling in payment.phpOpen payment.php and search for occurrences of 'patientid' to identify where this parameter is processedAffected if The patientid parameter is used in SQL queries within payment.php without proper sanitization or parameterized queries
-
Inspect SQL query construction for patientidExamine the code surrounding patientid usage to determine if user input is directly concatenated into SQL statements or if prepared statements are usedAffected if The patientid parameter is directly included in SQL queries without using prepared statements, binding parameters, or input sanitization functions
-
Test parameter for injection susceptibilityIf authorized and in a non-production environment, submit a benign SQL test payload (such as patientid=1' OR '1'='1) via GET or POST to /payment.php and observe database error responses or unexpected behaviorAffected if The application returns database errors, displays unexpected data, or behaves differently when SQL syntax is injected into the patientid parameter
A user is affected if they run itsourcecode Hospital Management System 1.0 with payment.php accessible and the patientid parameter is used in unsanitized SQL queries against a database
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 parameterized queries/prepared statements for the patientid parameter in payment.php, apply input validation, and ensure the database user follows least-privilege principles.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14773 — 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-14773 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