CVE-2026-14659: SQL Injection in itsourcecode Hospital Management System 1.0
A SQL injection vulnerability exists in itsourcecode Hospital Management System version 1.0 affecting the patient appointment functionality. An authenticated attacker can inject malicious SQL commands through the 'patiente' parameter in the /patientappointment.php file to read, modify, or delete database records. The vulnerability requires a valid user login but can be exploited remotely, and proof-of-concept details are publicly available.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 6.3 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
- Weaknesses (CWE)
- CWE-74, CWE-89
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-07-04 / 2026-07-06
NVD description (verbatim)
A 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.
6 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-14659 is a SQL injection flaw (CWE-89, CWE-74) in Hospital Management System 1.0's /patientappointment.php endpoint. The application fails to properly sanitize or parameterize the 'patiente' input parameter, allowing SQL commands to be embedded in HTTP requests. An authenticated user can manipulate this parameter to execute arbitrary SQL queries against the backend database. The CVSS 3.1 score of 6.3 (Medium severity) reflects the requirement for prior authentication (PR:L), though the impact spans confidentiality, integrity, and availability of patient data.
Business impact
Healthcare facilities using this system face exposure of sensitive patient health information, appointment records, and potentially billing data. An insider threat or compromised staff account could alter or delete critical appointment schedules, disrupting patient care delivery. Regulatory implications include HIPAA violations (in the US) and data protection law non-compliance depending on jurisdiction. Reputational damage and liability for unauthorized data access are significant secondary risks.
Affected systems
itsourcecode Hospital Management System version 1.0 is the only confirmed affected version. Organizations running this software on Internet-facing servers or within networks accessible to authenticated users are at risk. The vulnerability does not appear in the vendor product documentation provided; verify your deployment version against itsourcecode's official release notes.
Exploitability
The vulnerability is readily exploitable for attackers with valid credentials. Proof-of-concept code is publicly disclosed, lowering the barrier to exploitation. An attacker needs network access to the application and authentication credentials—either through compromise of a staff account, weak password enforcement, or insider access. No special tools beyond a standard HTTP client are required to craft and send malicious SQL payloads. The vulnerability is not currently listed in CISA's Known Exploited Vulnerabilities (KEV) catalog.
Remediation
Immediately update itsourcecode Hospital Management System to a patched version confirmed by the vendor to address this SQL injection. As an interim control, restrict network access to the application to trusted internal networks only and enforce strong authentication policies. Parameterized queries and prepared statements must be implemented across all user input handling. Conduct a security audit of the application code for similar SQL injection points.
Patch guidance
Contact itsourcecode directly or visit their official advisory page for patched version availability and deployment instructions. Verify patch version numbers against the vendor's security advisory before applying updates. Test patches in a non-production environment first, given the critical nature of hospital management systems. Prioritize patching based on the scope of authenticated users who have access to the /patientappointment.php endpoint.
Detection guidance
Monitor access logs for the /patientappointment.php endpoint for suspicious patterns—requests with SQL keywords (SELECT, UNION, DROP, INSERT, UPDATE, DELETE) in the patiente parameter, unusual character encoding, or repeated failed queries. Deploy Web Application Firewall (WAF) rules to block common SQL injection signatures. Enable database query logging and alert on unexpected or malformed SQL statements. Review staff access patterns to the patient appointment module for anomalies coinciding with the vulnerability disclosure date.
Why prioritize this
Although assigned a Medium severity score, this vulnerability affects protected health information and critical healthcare operations, elevating its operational priority. Public disclosure of proof-of-concept code increases short-term exploitation likelihood. The authentication requirement provides some defense but does not eliminate risk from insider threats or credential compromise. Organizations should treat this as high-priority for remediation despite the CVSS score.
Risk score, explained
The CVSS 3.1 score of 6.3 reflects a vulnerability that can be exploited remotely over the network (AV:N) with low complexity (AC:L), but requires a logged-in user (PR:L). The lack of user interaction (UI:N) means exploitation can be automated. Impact is assessed as low across confidentiality, integrity, and availability (C:L/I:L/A:L)—reflecting that the attacker has limited scope and cannot compromise the entire system. The Medium rating appropriately balances the authentication barrier against the sensitivity of healthcare data and public availability of exploit code.
Frequently asked questions
Can this vulnerability be exploited without a valid user account?
No. The CVSS vector (PR:L) indicates prior authentication is required. An attacker must have valid login credentials to exploit this SQL injection. However, weak password policies, credential reuse, or account compromise could provide an attacker with these credentials.
What patient data is at risk?
Any data accessible to the authenticated user through the application's database could be at risk, including appointment records, personal health information, contact details, and potentially billing or insurance information. The scope depends on the database permissions assigned to the application's service account.
Is there a workaround if we cannot patch immediately?
While not a substitute for patching, immediate mitigations include: restricting network access to the application to trusted IPs, enforcing multi-factor authentication for user logins, disabling the /patientappointment.php endpoint if not essential, and deploying a WAF with SQL injection signatures. However, these measures should be temporary—patching remains essential.
Should we assume this vulnerability has been exploited in the wild?
The vulnerability was disclosed to the public on July 4, 2026, and proof-of-concept code is available. We recommend assuming it may have been exploited, particularly if your system has been accessible to the internet or if user account logs show suspicious activity since the disclosure date. Conduct a database audit for unauthorized changes.
This analysis is provided for informational purposes to assist security professionals in vulnerability assessment and remediation planning. No guarantee is made regarding the completeness or accuracy of patch version numbers or vendor advisory details; always verify critical information directly with itsourcecode's official channels. This intelligence does not constitute legal, medical, or compliance advice. Organizations subject to HIPAA, GDPR, or other data protection regulations should consult legal and compliance teams regarding notification and remediation obligations. Proof-of-concept details have been disclosed publicly; do not attempt to execute exploit code against systems you do not own or have explicit permission to test. Source: NVD (public-domain), retrieved 2026-08-13. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-10155MEDIUMSQL Injection in Bdtask Multi-Store Inventory Management System 1.0
- CVE-2026-10170MEDIUMSQL Injection in code-projects Visitor Management System 1.0
- CVE-2026-10171MEDIUMSQL Injection in code-projects Online Music Site 1.0 AdminUpdateAlbum.php
- CVE-2026-10176MEDIUMSQL Injection in Aider-AI Aider 0.86.3 Code Generation
- CVE-2026-10193MEDIUMSQL Injection in OFCMS ComnController – Authentication Required
- CVE-2026-10202MEDIUMOFCMS 1.1.3 SQL Injection in SystemDictController
- CVE-2026-10203MEDIUMSQL Injection in OFCMS 1.1.3 JSON Query Interface
- CVE-2026-10204MEDIUMSQL Injection in OFCMS 1.1.3 JSON Query Interface