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

CVE-2026-42517

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 the use of reversible Base64 encoding for protecting sensitive data. An authenticated attacker could exploit this vulnerability by decoding and manipulating Base64-encoded parameters in the request URL to gain unauthorized access to sensitive information 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 · high confidence

e-Sushrut uses Base64 encoding to protect sensitive data in URL parameters. Since Base64 is merely encoding (not encryption), an authenticated attacker can easily decode these parameters, modify them, and resubmit requests to gain unauthorized access to sensitive information.

MitigationReplace Base64 encoding with proper authenticated encryption (e.g., AES-256-GCM) and implement server-side validation that does not trust encoded parameter values without verification.

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
    Locate the e-Sushrut application directory or check running services on the host. Common paths include /var/www/html/e-sushrut, C:\inetpub\wwwroot\e-sushrut, or check for e-Sushrut processes via 'tasklist' or 'ps' commands.
    Affected if e-Sushrut is installed and accessible on the system
  2. Identify Base64-encoded URL parameters in use
    Capture HTTP traffic to the e-Sushrut server using a proxy (Burp Suite, OWASP ZAP) or review server access logs for requests containing Base64 patterns (regex: [A-Za-z0-9+/=]{20,}). Look for URL parameters that decode to meaningful data like IDs, names, or file paths.
    Affected if URL parameters contain Base64-encoded values that can be decoded to sensitive information
  3. Verify sensitive data types in encoded parameters
    Decode captured Base64 parameters and inspect for sensitive content: patient health records, personal identifiable information (PII), authentication tokens, file paths, or database identifiers. Use a Base64 decoder on suspected parameter values.
    Affected if Decoded parameters reveal sensitive data such as patient records, credentials, or administrative identifiers
  4. Test parameter tampering for unauthorized access
    Take a captured Base64-encoded parameter value, decode it, modify the internal value (e.g., change a patient ID or user ID), re-encode to Base64, and resubmit the request. Observe if the application returns data belonging to other users or elevated privileges.
    Affected if Modifying and resubmitting decoded parameters grants access to unauthorized data or functionality
  5. Check application configuration for encoding practices
    Review e-Sushrut configuration files (typically in config/, settings/, or web.config) for any settings related to URL parameter encoding, security token handling, or data serialization methods. Look for references to Base64, encoding, or parameter protection mechanisms.
    Affected if Configuration explicitly uses Base64 encoding for protecting sensitive URL parameters

A system is affected if e-Sushrut is present and uses Base64-encoded URL parameters that, when decoded and modified, allow unauthorized access to sensitive information.

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

Replace Base64 encoding with proper authenticated encryption (e.g., AES-256-GCM) and implement server-side validation that does not trust encoded parameter values without verification.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing10.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,020
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42517 — 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-42517 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