dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-42515

HIGH · 7.1 CVSS v4.0 Published 2026-04-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
This vulnerability exists in e-Sushrut due to improper access control in resource access validation. An authenticated attacker could exploit this vulnerability by manipulating parameter in the API request URL to gain unauthorized access to sensitive information of patients on the targeted system.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability in e-Sushrut where the application fails to properly validate whether an authenticated user has authorization to access specific resources. An attacker with valid credentials can manipulate parameters in API request URLs to access sensitive patient data they should not have permission to view.

MitigationImplement proper authorization checks on all API endpoints to verify the authenticated user has permission to access the requested resource before returning any data. Additionally, implement object-level access control validation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm e-Sushrut installation exists
    Search for e-Sushrut application files, services, or web applications running on common ports (8080, 8443, 443). Check for e-Sushrut in installed applications or web server document roots.
    Affected if e-Sushrut is present in the environment
  2. Identify API endpoints accepting object identifiers
    Review application documentation, enumerate API routes, or use network traffic analysis to find endpoints that accept patient IDs, record IDs, or similar parameters in URLs (e.g., /api/patients/{id}, /api/records/{recordId}).
    Affected if API endpoints accept object identifiers as URL parameters without evident authorization checks
  3. Verify authentication is required for API access
    Attempt to access identified API endpoints without providing credentials. Confirm the application returns 401/403 rather than exposing data.
    Affected if API endpoints require authentication but may not enforce per-object authorization
  4. Test for IDOR by parameter manipulation
    Using valid credentials for one user, access an API endpoint with another user's patient record ID or resource identifier. Compare the response against what the authenticated user should legitimately access.
    Affected if Requesting a resource belonging to another user/patient returns data instead of a 403 Forbidden or error indicating access denied
  5. Inspect API response for cross-user data leakage
    Query the same API endpoint with different user credentials and different object IDs. Check whether responses consistently validate ownership or blindly return data based solely on valid authentication.
    Affected if Different authenticated users can retrieve each other's patient data by changing object identifiers in requests

A user is affected if they run e-Sushrut and can access patient records belonging to other users by simply changing object identifiers in API requests, indicating missing object-level authorization controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks on all API endpoints to verify the authenticated user has permission to access the requested resource before returning any data. Additionally, implement object-level access control validation.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42515 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42515 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data