/

CVE-2026-90858

Severity:

HIGH RISK

(7.3)

Authorization Bypass (CWE-285) in Online Clinic System

CVE-2026-90858

Deferred

Vulnerability type

Category:

Authorization Bypass

CWE:

CWE-285, CWE-639

Impact:

Unauthorized Access

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A remotely reachable authorization flaw in the online clinic management system may allow an attacker to manipulate the adminmail parameter during session handling.

Under conditions where authorization decisions rely on attacker-controlled account or identity data, this could permit access beyond the user's intended privileges.

Affected context

The issue occurs in the administrative application flow associated with session_start in adminappview.php. It may affect deployments where the adminmail request value influences session establishment or authorization decisions without sufficient server-side verification. Exploitability depends on the endpoint being remotely reachable and the application accepting manipulated identity-related input.

Exploit preconditions

  • Attack surface: A remotely accessible administrative application endpoint
  • Required access: Ability to send requests to the affected session-handling functionality; valid credentials may not be required if authorization is derived from attacker-controlled input
  • Trigger point: Processing of the adminmail argument during session or authorization handling
  • Why exploitation is possible: The application may trust or insufficiently validate user-controlled identity data when determining administrative access

Why this happens

The underlying bug is an authorization enforcement failure in which a request parameter can influence the identity or privilege associated with a session.

This maps primarily to CWE-285: Improper Authorization, because the application may grant access without reliably verifying that the requester is entitled to the requested administrative role. It is also related to CWE-639: Authorization Bypass Through User-Controlled Key, where an attacker-controlled identifier is used to select or represent a protected account or resource.

Potential impact

  • An attacker may gain unauthorized access to administrative functionality
  • Sensitive patient, clinic, or account information could be exposed
  • Attackers could modify records or application settings
  • Administrative capabilities could be misused to create persistence or affect service availability

General mitigation guidance

Mitigation generally focuses on making authorization decisions independent of untrusted request parameters.

Common defensive patterns include:

  • Deriving the authenticated identity from a securely managed server-side session rather than request parameters
  • Enforcing authorization checks on every protected operation
  • Binding sessions to verified authentication context and server-side account records
  • Validating identifiers against the authenticated principal and applying deny-by-default access rules
  • Applying least privilege to administrative roles and service accounts
  • Avoiding exposure of administrative endpoints when they are not required to be remotely reachable

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis rules identifying request parameters used in session creation or privilege decisions
  • Code review checks for authorization logic based on email addresses, usernames, or other client-supplied identifiers
  • Dynamic tests that alter identity-related parameters while comparing access decisions across accounts
  • Audit logging for administrative session creation, privilege changes, and access to protected records
  • Policy enforcement requiring centralized authorization middleware for sensitive endpoints
  • Automated security review tools that flag user-controlled values flowing into authentication or authorization logic

Sources

SourceLink
github.comgithub.com/subhajitkhan/online-clinic-management-system/
github.comgithub.com/subhajitkhan/online-clinic-management-system/issues/4
vuldb.comvuldb.com/cve/CVE-2026-90858
vuldb.comvuldb.com/submit/927291
vuldb.comvuldb.com/vuln/403415
vuldb.comvuldb.com/vuln/403415/cti

Frequently asked

questions

The reported flaw is described as remotely reachable. Practical exploitability depends on network exposure, endpoint availability, and whether additional authentication controls are enforced.

An attacker generally needs the ability to submit requests to the affected session-handling functionality. Whether valid credentials are required depends on how the deployment establishes and verifies sessions.

Authorization should be based on a server-side authenticated session and verified account context, not on a client-controlled adminmail value or similar request parameter.

Use centralized, deny-by-default authorization checks; test privilege boundaries with altered identifiers; minimize administrative exposure; and monitor unusual administrative session activity.

Find out what's already
exploitable in your codebase.