What is CVE-2026-104637?

CVE-2026-104637 is onetwothreeneth HospitalManagementSystem controller.php edit_patient unrestricted upload. The supplied enrichment data classifies it as File Upload mapped to CWE-434 Unrestricted Upload of File with Dangerous Type; CWE-284 Improper Access Control.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-104637. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-104637 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

1133 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-104637 using CVSS 7.3, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

highFile Uploadpublic exploit

CVE-2026-104637

CVE-2026-104637 — onetwothreeneth HospitalManagementSystem controller.php edit_patient unrestricted upload

A weakness has been identified in onetwothreeneth HospitalManagementSystem up to 9ef91ed6007314b6473110ed699dff76d158f61d. The affected element is the function add_patient/add_physician/add_account/update_account/update_subaccount/edit_physician/edit_patient of the file php/controller.php. Executing a manipulation of the argument img can lead to unrestricted upload. The attack may be launched remotely. The exploit has been made available to the public and could be used for attacks. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases. The project was informed of the problem early through an issue report but has not responded yet.

Published Oct 2, 2026Updated Oct 2, 2026Sources: NVD, onetwothreeneth (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

ahead of 0% of scored CVEs

Affects

onetwothreeneth

HospitalManagementSystem

CVSS base

7.3

high · 6 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade HospitalManagementSystem to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
onetwothreeneth	HospitalManagementSystem	9ef91ed6007314b6473110ed699dff76d158f61d	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

Low

Confidentiality

Low

Integrity

Low

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
7.3	CVSS 3.1	high	3.9	3.4	NVD, GHSA
7.5	CVSS 2.0	high	10	6.4	vuldb.com (CNA)
6.9	CVSS 4.0	medium	—	—	onetwothreeneth (CNA)
7.3	CVSS 3.1	high	—	—	onetwothreeneth (CNA)
7.3	CVSS 3.0	high	—	—	onetwothreeneth (CNA)
7.5	CVSS 2.0	high	—	—	onetwothreeneth (CNA)

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-284 · Improper Access Control

Varies by Context::

Mitigation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.

CWE-434 · Unrestricted Upload of File with Dangerous Type

Execute Unauthorized Code or Commands

Mitigation: Generate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.[REF-422] [REF-423]

Weakness & attack patterns

CWE-434Unrestricted Upload of File with Dangerous Type
CWE-284Improper Access Control

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-478 · Modification of Windows Service ConfigurationCAPEC-558 · Replace Trusted ExecutableCAPEC-441 · Malicious Logic InsertionCAPEC-546 · Probe Application MemoryCAPEC-502 · Intent SpoofCAPEC-562 · Modify Shared FileCAPEC-551 · Modify Existing ServiceCAPEC-536 · Data Injected During ConfigurationCAPEC-564 · Run Software at LogonCAPEC-550 · Install New ServiceCAPEC-19 · Embedding Scripts within ScriptsCAPEC-503 · WebView Exposure

T1574.010Hijack Execution Flow: ServicesFile Permissions Weakness
T1027.009Obfuscated Files or Information: Embedded Payloads
T1546.004Event Triggered Execution: .bash_profile and .bashrc

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

1,133

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Search application, proxy, and WAF logs for requests touching /add_physician/add_account/update_account/update_subaccount/edit_physician/edit_patient, /controller.php.
Prioritize edge telemetry for network-reachable HospitalManagementSystem.
Monitor for scanner or exploit-pattern traffic after 1133 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 7.3 (AV:N)
Oct 2, 2026 · NVD
Initial · CVE published
Oct 2, 2026 · NVD
Reported · Advisory disclosed
Oct 2, 2026 · onetwothreeneth
Reported · VulDB entry created
Oct 2, 2026 · onetwothreeneth
Reported · VulDB entry last update
Oct 2, 2026 · onetwothreeneth
Added · GHSA-vwxr-mjcp-6whc published (medium)
Oct 2, 2026 · GitHub Security Advisory
CVE published by MITRE.
Oct 2, 2026 · SOCRadar CTI

Source activity

Readings a source repeats on a schedule, counted rather than listed.

2×ModifiedOct 2, 2026 · SOCRadar CTI

References

8 on the record

github.com/onetwothreeneth/HospitalManagementSystem/
Exploit, Third Party Advisory, NIST
github.com/onetwothreeneth/HospitalManagementSystem/issues/5
Exploit, Third Party Advisory, NIST
vuldb.com/cve/CVE-2026-104637
Vendor Advisory
vuldb.com/submit/963707
Vendor Advisory
vuldb.com/vuln/412925
Vendor Advisory
vuldb.com/vuln/412925/cti
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2026-104637
NVD
github.com/advisories/GHSA-vwxr-mjcp-6whc
Exploit, Third Party Advisory

Elsewhere on this site

onetwothreenethevery CVE for this vendor
File Uploadsame class
CWE-434other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-104637 is onetwothreeneth HospitalManagementSystem controller.php edit_patient unrestricted upload, a high vulnerability affecting HospitalManagementSystem from onetwothreeneth. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-104637. Public exploit evidence is: 1133 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.3 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.