CVE Alert: CVE-2026-86262 – sfturing – hosp_order

A security vulnerability has been detected in sfturing hosp_order up to 627f426331da8086ce8fff2017d65b1ddef384f8. This affects the function updateOrderSta1/updateOrderdiseaseInfo of the file ssm_pro/src/main/java/cn/sfturing/web/OrderController.java of the component Order Handler. The manipulation of the argument userID/id leads to authorization bypass. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The project was informed of the problem early through an issue report but has not responded yet.

**Risk verdict:** High operational urgency: this is a remotely exploitable authorisation weakness with public exploit material, although KEV, SSVC exploitation status and EPSS data are not provided.

**Why this matters:** An unauthorised party may alter order or disease-related information, undermining clinical workflow, data integrity and audit reliability. Likely attacker goals include fraudulent order manipulation, disruption of care processes, privacy-impacting data changes, or preparation for broader compromise through trusted application access.

**Most likely attack path:** An attacker can reach the order-handling interface over the network without authentication, user interaction or meaningful exploitation complexity. Supplying another patient or order identifier in the relevant `userID`/`id` parameters may allow cross-record modification; the unchanged scope limits direct platform escape, but affected records could create consequential downstream harm.

**Who is most exposed:** Internet-facing or partner-accessible hospital deployments, particularly installations exposing order APIs without a gateway, strong identity enforcement or network segmentation. Shared-service environments and sites relying on default application authorisation are especially at risk.

Alert on unauthorised or cross-user changes to order and disease fields.

Correlate requests where caller identity differs from supplied `userID`/`id`.

Review unusual bulk updates, sequential identifier probing and failed-then-successful requests.

Preserve application, API gateway and database audit trails for affected records.

Mitigation and prioritisation:

Apply the highest-confidence vendor or source-level fix immediately; no confirmed remediation is supplied.

Enforce server-side object-level authorisation, ignoring client-supplied ownership claims.

Restrict exposure with VPN/API gateways and segment clinical systems.

Validate in staging, then expedite emergency change approval and retrospective record review.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.