/

CVE-2026-86214

Severity:

HIGH RISK

(7.3)

Improper Authentication (CWE-287) in College System

CVE-2026-86214

Deferred

Vulnerability type

Category:

Improper Authentication

CWE:

CWE-287

Impact:

Authentication Bypass and 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

CVE-2026-86214 is an improper authentication vulnerability in the College-Management-System's Front-end/login.php component. Remote attackers may be able to manipulate the email argument to bypass or weaken authentication when the login flow does not properly verify supplied identity information.

Affected context

The vulnerability is associated with the login functionality of Mstfakts College-Management-System, specifically an unknown function in Front-end/login.php. It becomes risky when email-based authentication decisions rely on insufficient validation or fail to bind the supplied identifier to a correctly verified account and credential set. The product uses a rolling-release model, so affected deployment states may vary.

Exploit preconditions

  • Attack surface: The remotely accessible login endpoint
  • Required access: Network access to the application's authentication interface; valid credentials may not be required if the flaw permits authentication bypass
  • Trigger point: Processing of the email argument during login
  • Why exploitation is possible: Authentication logic may accept manipulated identity input without consistently verifying the complete authentication state

Why this happens

The underlying bug is an authentication decision that insufficiently validates or correlates user-controlled identity data. When an email value can influence account selection or authentication success without dependable credential verification and authorization checks, an attacker may obtain access as an unintended user. This behavior maps to CWE-287: Improper Authentication, in which the application fails to adequately establish that a requester is the claimed identity.

Potential impact

  • An attacker may bypass the login process
  • Unauthorized users could access protected application functions or records
  • Account information may be exposed or modified
  • An attacker could impersonate another account
  • Compromised accounts could be used for further activity within the application

General mitigation guidance

Mitigation generally focuses on making authentication decisions independent of untrusted, insufficiently verified identifiers.

Common defensive patterns include:

  • Verifying passwords or other authentication factors through a trusted server-side identity process
  • Treating email addresses as account identifiers rather than proof of identity
  • Applying strict input normalization and validation without using it as a substitute for authentication
  • Binding authenticated sessions to the account established by successful credential verification
  • Enforcing authorization checks for every protected operation
  • Limiting account and application privileges according to least-privilege principles
  • Adding regression tests for altered, duplicated, missing, and boundary-case email values

How teams detect issues like this

Organizations can assess this class of issue through:

  • Static analysis and code review of login handlers, especially branches that use email input to select accounts or determine authentication success
  • Tests that compare authentication outcomes for valid, invalid, altered, and cross-account identifiers
  • Monitoring for successful sessions that lack corresponding verified credential events
  • Web application policy checks requiring server-side authentication and authorization before protected responses
  • Automated security testing or code review tools that flag user-controlled identity fields used directly in authentication decisions

Sources

SourceLink
github.comgithub.com/Mstfakts/College-Management-System/issues/6
vuldb.comvuldb.com/cve/CVE-2026-86214
vuldb.comvuldb.com/submit/897250
vuldb.comvuldb.com/vuln/399350
vuldb.comvuldb.com/vuln/399350/cti

Frequently asked

questions

Yes. The reported attack surface is the remotely accessible login functionality, although the exact exploitability depends on deployment exposure and the behavior of the affected authentication code.

Not necessarily. If manipulated email input can cause authentication to succeed without proper credential verification, an attacker may not need a valid account password.

Make successful authentication depend on independently verified credentials or authentication factors, and use the resulting server-side identity for session creation and authorization.

Review all identity-related login branches, test negative and cross-account cases, enforce authorization after authentication, and monitor for sessions created without a corresponding successful verification event.

Find out what's already
exploitable in your codebase.