CVE-2026-10184: SourceCodester Hospitals Patient Records Management System Users.php delete sql injection
A security flaw has been discovered in SourceCodester Hospitals Patient Records Management System 1.0. This impacts an unknown function of the file /classes/Users.php?f=delete. The manipulation of the argument ID results in sql injection. The attack may be launched remotely. The exploit has been released to the public and may be used for attacks.
Security readout for executives and security teams
Plain-English summary
CVE-2026-10184 is a SQL injection in SourceCodester Hospitals Patient Records Management System 1.0. A remote attacker could manipulate the delete user request and potentially read, change, or disrupt database-backed records. Public proof-of-concept exploit material is referenced, but the bundle does not show confirmed active exploitation.
Executive priority
Treat this as urgent for any deployed instance because it concerns patient-record software, remote database impact, and public exploit availability. If the product is not in use, document non-exposure and move on.
Technical view
The reported flaw affects /classes/Users.php?f=delete, where the ID argument is not safely handled, resulting in CWE-89 SQL injection. VulDB rates it high with CVSS v2 7.5, network attack vector, low complexity, and no authentication in the vector. Evidence names version 1.0 only.
Likely exposure
Likely exposure is limited to organizations running SourceCodester Hospitals Patient Records Management System 1.0. Risk is highest where the application or user-management functions are reachable from untrusted networks. The source bundle does not provide install prevalence or hosted-service exposure data.
Exploitation context
The sources say an exploit has been publicly released and may be used for attacks. CISA KEV status is false in the bundle, so active exploitation should not be claimed from this evidence alone.
Researcher notes
Evidence is mainly VulDB/CVE-sourced and identifies the vulnerable file, parameter, product, and version. The bundle does not include a vendor patch, detailed root-cause diff, affected deployment prerequisites, or confirmed exploitation telemetry.
Mitigation direction
Check SourceCodester or project guidance for an official fix or replacement version.
Restrict access to the application, especially administrative and user-management functions.
Back up and review the application database for suspicious changes.
Prioritize removal or isolation if no vendor patch is available.
Ensure SQL queries use parameterized statements before redeploying internally.
Validation and detection
Inventory systems for Hospitals Patient Records Management System version 1.0.
Confirm whether /classes/Users.php?f=delete is reachable from untrusted networks.
Review web and database logs for unusual delete-user requests or SQL errors.
Verify whether any vendor update or local secure-query patch is applied.
Confirm backups and restoration procedures for patient-record databases.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-74 · source CWE mapping
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.