CVE-2026-14659
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 has been found in itsourcecode Hospital Management System 1.0. Impacted is an unknown function of the file /patientappointment.php. Such manipulation of the argument patiente leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the 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 itsourcecode Hospital Management System 1.0 allows remote attackers to inject malicious SQL queries via the 'patiente' parameter in /patientappointment.php. The lack of proper input sanitization or parameterized queries enables database manipulation.
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.
-
Verify Hospital Management System installationLocate the itsourcecode Hospital Management System installation directory and confirm the application files are present. Common paths may include /var/www/html/, /www/, or C:\inetpub\wwwroot\ depending on the web server environment.Affected if The itsourcecode Hospital Management System is installed and running.
-
Confirm application version is 1.0Check for a version file, README, or any version indicator within the application root directory. Look for version.php, about.php, or check the main index page source for version information.Affected if The installed version is 1.0.
-
Verify patientappointment.php existsLocate the patientappointment.php file within the web application directory structure. This file handles patient appointment functionality and contains the vulnerable parameter handler.Affected if The file patientappointment.php exists in the application.
-
Inspect the patiente parameter handlingOpen patientappointment.php and search for the 'patiente' parameter usage in database queries. Look for SQL statements that directly incorporate this parameter without prepared statements, parameter binding, or evident input sanitization functions.Affected if The patiente parameter is used in SQL queries without parameterized queries or input sanitization.
-
Check database user privilegesIf access to the application source is limited, verify the database configuration file to determine what database user privileges are configured for the application.Affected if The application database user has privileges that would allow SQL injection to manipulate the database.
A user is affected if they are running itsourcecode Hospital Management System version 1.0 with the patientappointment.php file present and the patiente parameter being processed in SQL queries without prepared statements or sanitization.
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 involving the patiente parameter in patientappointment.php, or apply robust input validation and output encoding.
- 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-14659 — 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-14659 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