CVE-2026-10185: SourceCodester Hospitals Patient Records Management System Users.php save sql injection
A weakness has been identified in SourceCodester Hospitals Patient Records Management System 1.0. Affected is an unknown function of the file /classes/Users.php?f=save. This manipulation of the argument ID causes sql injection. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks.
Security readout for executives and security teams
Plain-English summary
A hospital patient records application has a SQL injection flaw that could let a remote attacker read, change, or disrupt database-backed records. The sources identify SourceCodester Hospitals Patient Records Management System 1.0 only. Public exploit material is reported, but active exploitation is not confirmed.
Executive priority
Prioritize urgently if this application is internet-facing or stores real patient data. The likely business impact is confidentiality, integrity, and availability risk to medical records. If the product is not deployed, document non-exposure and monitor for related advisories.
Technical view
CVE-2026-10185 is reported as SQL injection in /classes/Users.php?f=save through the ID argument. The CVSS v2 vector is AV:N/AC:L/Au:N/C:P/I:P/A:P, score 7.5. CWEs listed are CWE-74 and CWE-89. The affected product evidence is limited to version 1.0.
Likely exposure
Exposure is likely where SourceCodester Hospitals Patient Records Management System 1.0 is deployed and reachable over a network, especially if the affected user-save endpoint is exposed. The source bundle does not identify hosted services, forks, or other versions as affected.
Exploitation context
The provided sources say remote exploitation is possible and public exploit material exists. KEV is false, and no cited source confirms active exploitation in the wild. Treat public-facing deployments as higher risk because the CVSS vector indicates no authentication is required.
Researcher notes
The report names the endpoint and ID argument but describes the affected function as unknown. Do not extrapolate to other SourceCodester products or versions. Evidence is strongest for the VulDB/CVE description and public issue reference; remediation evidence is incomplete.
Mitigation direction
Inventory deployments of SourceCodester Hospitals Patient Records Management System 1.0.
Remove public access to the affected application until vendor guidance is reviewed.
Check SourceCodester or project guidance for any official patch or replacement release.
Restrict access to trusted networks and authenticated administrative users where possible.
Review database privileges used by the application and reduce unnecessary write permissions.
Validation and detection
Confirm whether version 1.0 is deployed in production or test environments.
Verify whether /classes/Users.php?f=save is reachable from untrusted networks.
Review application code for parameterized database queries around the ID argument.
Search application and web logs for suspicious requests to the affected endpoint.
Confirm whether any vendor update or local hardening has been applied.
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.