CVE Intelligence
Skip to main content
mediumAccess Control

CVE-2026-90851

CVE-2026-90851 — PHPGurukul Hostel Management System checklogin.php access control

A flaw has been found in PHPGurukul Hostel Management System 3.0. This affects an unknown part of the file /admin/includes/checklogin.php. This manipulation of the argument ID causes improper access controls. Remote exploitation of the attack is possible. The exploit has been published and may be used.

Published Updated Sources: NVD, PHPGurukul (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

ahead of 0% of scored CVEs

Affects

PHPGurukul

Hostel Management System

CVSS base

6.3

medium · 6 sources

Remediation

The vendor's own words where we have them.

Upgrade Hostel Management System to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Prioritize based on EPSS, PoC availability, and external exposure.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

VendorProductVersionsStatus
PHPGurukulHostel Management System3.0Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

Low

Confidentiality

Low

Integrity

Low

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
6.3CVSS 3.1medium2.83.4NVD, GHSA
6.5CVSS 2.0medium86.4vuldb.com (CNA)
5.3CVSS 4.0medium——PHPGurukul (CNA)
6.3CVSS 3.1medium——PHPGurukul (CNA)
6.3CVSS 3.0medium——PHPGurukul (CNA)
6.5CVSS 2.0medium——PHPGurukul (CNA)

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-266 · Incorrect Privilege Assignment

  • Gain Privileges or Assume Identity

Mitigation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.

CWE-284 · Improper Access Control

  • Varies by Context::

Mitigation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.

Weakness & attack patterns

  • CWE-284Improper Access Control
  • CWE-266

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-562 · Modify Shared FileCAPEC-19 · Embedding Scripts within ScriptsCAPEC-503 · WebView ExposureCAPEC-441 · Malicious Logic InsertionCAPEC-563 · Add Malicious File to Shared WebrootCAPEC-478 · Modification of Windows Service ConfigurationCAPEC-479 · Malicious Root CertificateCAPEC-502 · Intent SpoofCAPEC-536 · Data Injected During ConfigurationCAPEC-546 · Probe Application MemoryCAPEC-550 · Install New ServiceCAPEC-551 · Modify Existing Service
  • T1027.009Obfuscated Files or Information: Embedded Payloads
  • T1546.004Event Triggered Execution: .bash_profile and .bashrc
  • T1546.016Event Triggered Execution: Installer Packages

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Search application, proxy, and WAF logs for requests touching /admin/includes/checklogin.php.
  • Prioritize edge telemetry for network-reachable Hostel Management System.
web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026
  2. Added · CVSS 3.1 6.3 (AV:N)

    Sep 15, 2026 · NVD

  3. Initial · CVE published

    Sep 15, 2026 · NVD

  4. Added · GHSA-fqcp-p9cx-qvwf published (low)

    Sep 15, 2026 · GitHub Security Advisory

  5. CVE published by MITRE.

    Sep 15, 2026 · SOCRadar CTI

  6. Reported · Advisory disclosed

    Sep 14, 2026 · PHPGurukul

  7. Reported · VulDB entry created

    Sep 14, 2026 · PHPGurukul

  8. Reported · VulDB entry last update

    Sep 14, 2026 · PHPGurukul

References

8 on the record

Coverage

1 story from the feeds we poll

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2026-90851 is PHPGurukul Hostel Management System checklogin.php access control, a medium vulnerability affecting Hostel Management System from PHPGurukul. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-90851. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-90851. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 6.3 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.