/

CVE-2026-85512

Severity:

HIGH RISK

(7.3)

Missing Authorization (CWE-862) in Class Exam System

CVE-2026-85512

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862, CWE-863

Impact:

Unauthorized access to administrative functionality or data

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

SourceCodester Class and Exam Timetabling System 1.0 contains a missing authorization check in the administrative session handling path. A remote attacker who can reach the affected endpoint may manipulate the ID argument to access functionality or resources without the required authorization.

Affected context

The issue occurs in the application's administrative interface, specifically around /admin/session.php, when an identifier supplied by a remote request is processed without consistently verifying that the current user is authorized to access the referenced object or operation. Risk is higher when the endpoint is internet-accessible and relies on client-supplied IDs for access decisions.

Exploit preconditions

  • Attack surface: Remotely accessible administrative web endpoint
  • Required access: A network path to the affected application; valid authentication may or may not be required depending on deployment and session handling
  • Trigger point: Processing of the ID argument in /admin/session.php
  • Why exploitation is possible: The application may identify a target resource or action from attacker-controlled input without enforcing an authorization check for the current principal

Why this happens

The underlying bug is an authorization failure in which authentication or session presence is treated as sufficient without verifying permission for the requested resource or operation. When a server trusts a client-controlled identifier and omits an object-level or function-level access check, an unauthorized user may reach administrative behavior. This primarily maps to CWE-862, Missing Authorization, and may also involve CWE-863, Incorrect Authorization, when an authorization check exists but is incomplete or incorrectly applied.

Potential impact

  • An attacker may access administrative resources without the intended permission.
  • An attacker could view or alter data associated with another user or object.
  • Unauthorized actions may be performed within the timetabling system.
  • The application could suffer data integrity, confidentiality, or availability impacts.

General mitigation guidance

Mitigation generally focuses on enforcing authorization on the server for

every protected operation and resource.

Common defensive patterns include:

  • Deriving authorization decisions from the authenticated server-side identity rather than trusting client-supplied identifiers.
  • Applying centralized, deny-by-default authorization middleware to administrative routes.
  • Performing object-level checks after resolving an identifier and before reading or modifying the object.
  • Separating authentication, authorization, and input validation responsibilities.
  • Using least-privilege roles and limiting administrative capabilities to only the users and services that require them.
  • Avoiding disclosure of sensitive resource details in authorization failure responses.

How teams detect issues like this

Organizations commonly identify missing authorization through:

  • Static analysis rules for routes that use request parameters to retrieve or modify records without nearby permission checks.
  • Code review checks for direct trust in ID-like parameters and inconsistent protection of administrative endpoints.
  • Dynamic testing that compares access decisions across users with different roles and ownership relationships.
  • Policy enforcement requiring centralized authorization middleware and negative access-control tests for protected routes.
  • Web application monitoring for repeated identifier changes, denied administrative requests, and unusual access across object boundaries.

Automated security review tools may help flag incomplete authorization paths, but findings should be validated against the application's intended access model.

Sources

SourceLink
github.comgithub.com/justconter/cve/issues/7
vuldb.comvuldb.com/cve/CVE-2026-85512
vuldb.comvuldb.com/submit/895057
vuldb.comvuldb.com/vuln/398677
vuldb.comvuldb.com/vuln/398677/cti
sourcecodester.comsourcecodester.com/

Frequently asked

questions

Yes. The affected endpoint can be reached remotely, although practical

exploitability depends on network exposure, session requirements, and the

application's deployment controls.

The available description does not establish a definitive authentication

requirement. Access to the endpoint and the behavior of its session checks

determine whether an unauthenticated user or a lower-privileged account can

trigger the issue.

Enforce server-side, object-level and function-level authorization for every

request, using the authenticated identity and server-controlled policy rather

than the supplied ID alone.

Use deny-by-default access policies, centralized authorization checks,

least-privilege roles, and automated tests that verify both permitted and

denied access for each administrative operation.

Find out what's already
exploitable in your codebase.