Summary
A high-severity authorization vulnerability in sfturing hosp_order allows a remote attacker to manipulate userID or id values processed by order-management endpoints. When access checks rely on these client-controlled identifiers, an attacker may access or modify order-related information belonging to another user.
Affected context
The issue occurs in the Order Handler component, specifically in the updateOrderSta1 and updateOrderdiseaseInfo functions of OrderController.java. It becomes risky when the application uses request-supplied userID or id values to identify protected records without reliably verifying that the authenticated requester is authorized to access those records. The affected project follows a rolling-release model, so a fixed release boundary cannot be determined from the available information.
Exploit preconditions
- Attack surface: Remotely reachable order-management request handlers
- Required access: An attacker may need a valid application session or other ability to submit requests, depending on endpoint exposure and authentication controls
- Trigger point: Processing of userID or id parameters by the affected order update functions
- Why exploitation is possible: Authorization decisions may trust user-controlled identifiers instead of independently binding the requested record to the authenticated user's permitted scope
Why this happens
The underlying bug is an object-level authorization failure, commonly associated with CWE-639: Authorization Bypass Through User-Controlled Key and related to CWE-285: Improper Authorization. The insecure pattern occurs when an application accepts an identifier from a request and uses it to retrieve or update a protected object without performing a server-side ownership, tenant, role, or capability check. Authentication alone does not establish authorization for every record selected by that identifier.
Potential impact
- An attacker may view order information belonging to other users
- An attacker could modify order status or disease-related order details
- Sensitive personal or medical-related information may be exposed
- Data integrity may be affected across accounts or organizational boundaries
- The vulnerability could support broader account or workflow abuse
General mitigation guidance
Mitigation typically focuses on enforcing authorization at the object and operation level rather than trusting request identifiers.
Common defensive patterns include:
- Deriving the target user or ownership scope from the authenticated server-side identity where possible
- Performing explicit authorization checks for every read and update operation
- Applying tenant, role, ownership, and workflow-state constraints consistently
- Treating userID and id values as untrusted selectors and validating them against permitted resources
- Using deny-by-default access policies and least-privilege service accounts
- Avoiding response differences that disclose whether another user's record exists
- Centralizing authorization logic to reduce inconsistent checks across controllers
How teams detect issues like this
Organizations commonly detect this class of issue through:
- Static analysis rules that identify direct use of request parameters in record lookups or updates
- Code review checks for missing ownership, tenant, role, or capability validation
- Dynamic tests that substitute identifiers belonging to another user or tenant
- API policy tests confirming that authenticated identities cannot cross object boundaries
- Logging and monitoring for repeated identifier enumeration or denied cross-account access attempts
- Automated security review tools that flag object-level authorization gaps

