CVE-2026-124646 in e-Sushrutinfo

Summary

by MITRE • 11/17/2026

This vulnerability exists in e-Sushrut HMIS due to insufficient server side object level authorization validation in the API endpoint. An unauthenticated remote attacker could exploit this vulnerability by modifying the parameter value in the API request.

Successful exploitation of this vulnerability could allow the attacker to enumerate and gain unauthorized access to sensitive information of patients on the targeted healthcare organization.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 11/17/2026

The identified security flaw resides within e-Sushrut Hospital Management Information System, specifically manifesting as an insufficient server-side object level authorization validation failure in its application programming interface endpoints. This architectural weakness indicates that the system fails to adequately verify whether the authenticated user or session context possesses the necessary permissions to access specific data objects requested via API calls. In a properly secured implementation, every request for sensitive resources must be cross-referenced against an access control list or role-based permission matrix on the server side before any processing occurs. However, in this instance, the application relies heavily on client-side controls or lacks robust validation logic that ensures the requesting entity is authorized to view the specific patient record being accessed. This oversight creates a critical gap where identity verification does not translate into proper resource authorization checks.

An unauthenticated remote attacker can exploit this vulnerability by manipulating parameter values within API requests to target arbitrary patient records. By altering identifiers such as user IDs, session tokens, or direct object references in the request payload, the attacker bypasses standard access controls that would normally restrict data visibility to authorized medical staff only. Since the server does not rigorously validate these parameters against the actual permissions of the requester, it returns the requested sensitive information regardless of whether the caller has legitimate business justification for accessing that specific patient's data. This mechanism allows for systematic enumeration of records by iterating through sequential or predictable identifiers, effectively turning a single endpoint into a comprehensive database extraction tool without requiring valid credentials for each individual record access.

The operational impact of this vulnerability is severe given the sensitive nature of healthcare data involved. Successful exploitation enables the unauthorized disclosure of protected health information including patient names, medical histories, diagnostic results, and potentially financial or insurance details. This breach violates fundamental principles of confidentiality within the CIA triad and directly contravenes regulatory frameworks such as HIPAA in the United States or GDPR in Europe which mandate strict access controls for personal data. The ability to enumerate records means that an attacker can harvest large volumes of sensitive information rapidly, leading to potential identity theft, medical fraud, blackmail, or reputational damage for both patients and the healthcare organization hosting the system.

This vulnerability aligns with CWE-284 Improper Access Control, specifically reflecting issues related to insufficient authorization checks on server-side resources. It also maps closely to MITRE ATT&CK technique T1078 Valid Accounts if authentication is partially bypassed or leveraged for initial access, though in this case the lack of object-level validation allows exploitation even with minimal or no valid session context depending on implementation details. To mitigate this risk, developers must implement robust server-side authorization checks that validate user permissions against every requested resource ID before returning data. Implementing role-based access control ensures that users can only interact with resources explicitly assigned to their roles. Additionally, employing indirect object references rather than direct identifiers in API parameters can obscure the structure of records and make enumeration more difficult, although this should complement rather than replace strict server-side validation. Regular security testing including automated penetration tests focusing on broken access control patterns is essential to detect such flaws before deployment.

Responsible

CERT-In

Reservation

11/09/2026

Disclosure

11/17/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!