/

CVE-2026-90840

Severity:

HIGH RISK

(7.3)

Improper Authentication (CWE-287) in PHPGurukul Admin

CVE-2026-90840

Deferred

Vulnerability type

Category:

Improper Authentication

CWE:

CWE-287

Impact:

Unauthorized Administrative 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

PHPGurukul Blood Donor Management System 1.0 contains an improper authentication flaw in the admin Dashboard controller. A remote attacker may be able to bypass or weaken authentication controls when the affected controller processes requests, potentially gaining unauthorized administrative access.

Affected context

The vulnerability occurs in the Admin Controllers component, specifically the __construct function in /application/controllers/admin/Dashboard.php. It is relevant when the application exposes the affected administrative route remotely and authentication checks are missing, incomplete, or incorrectly applied during controller initialization.

Exploit preconditions

  • Attack surface: Remotely accessible web application administrative functionality
  • Required access: The attacker may not need valid administrative credentials if the authentication weakness permits bypass
  • Trigger point: Request handling that invokes the Dashboard controller constructor
  • Why exploitation is possible: Authentication enforcement is improperly implemented, allowing a request to reach protected functionality without the expected verification

Why this happens

The underlying bug is an authentication-control failure in the admin controller lifecycle. The application does not reliably verify the caller's identity before allowing access to protected administrative functionality, which maps to CWE-287: Improper Authentication. This class of weakness can result from missing checks, checks performed at the wrong point, or trust in client-controlled authentication state.

Potential impact

  • An attacker could access administrative functionality without proper authorization.
  • Unauthorized users may be able to view or modify donor, user, or application data.
  • The application could experience configuration tampering or administrative account compromise.
  • The flaw may enable further attacks against connected services or stored sensitive information.

General mitigation guidance

Mitigation generally focuses on making authentication consistent, centralized, and mandatory for every protected administrative route.

Common defensive patterns include:

  • Enforcing server-side authentication before controller actions or sensitive data are reached.
  • Using a centralized authorization mechanism rather than relying on individual controller assumptions.
  • Avoiding trust in client-controlled identity, session, or privilege indicators.
  • Applying least privilege to administrative roles and service accounts.
  • Returning uniform authentication failures without exposing sensitive implementation details.
  • Protecting administrative interfaces with additional network, session, and policy controls where appropriate.

How teams detect issues like this

Detection approaches can include:

  • Static analysis for controllers or routes that access administrative functions without enforced authentication middleware.
  • Code review checks for missing, conditional, or late authentication checks in constructors and request handlers.
  • Dynamic testing that compares responses to protected endpoints with authenticated and unauthenticated requests.
  • Web application monitoring for successful administrative requests from unauthenticated sessions.
  • Policy enforcement requiring all administrative routes to declare authentication and authorization requirements.

Automated security review tools may help identify inconsistent protection across controller paths.

Sources

SourceLink
github.comgithub.com/usernamevnq/CVEs/issues/1
phpgurukul.comphpgurukul.com/
vuldb.comvuldb.com/cve/CVE-2026-90840
vuldb.comvuldb.com/submit/925615
vuldb.comvuldb.com/vuln/403392
vuldb.comvuldb.com/vuln/403392/cti

Frequently asked

questions

Yes. The affected administrative controller can be reached through the application's remote web interface, although successful exploitation depends on deployment exposure and the exact authentication flow.

Not necessarily. The authentication weakness may allow an attacker to reach protected functionality without the credentials normally required for administrative access.

Require centralized, server-side authentication and authorization before every administrative route and sensitive controller action is processed.

Use deny-by-default access policies, test protected endpoints without credentials, review controller initialization paths, and monitor for unexpected administrative activity.

Find out what's already
exploitable in your codebase.