/

CVE-2026-86277

Severity:

HIGH RISK

(7.3)

Authorization Bypass (CWE-285) in Syllabus LMS System

CVE-2026-86277

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-285, CWE-639

Impact:

Unauthorized deletion of examination 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 Syllabus-Aligned Learning Management & Examination System 1.0 contains an authorization bypass in the exam deletion functionality. A remote attacker who can reach the affected endpoint may manipulate the exam identifier and delete records without the intended authorization checks.

Affected context

The vulnerability occurs in the application's exam-management workflow, specifically the request handling associated with delete_exam.php. It becomes risky when the endpoint relies on a client-supplied exam identifier without consistently verifying that the requesting user is authorized to perform the deletion.

Exploit preconditions

  • Attack surface: The remotely accessible exam deletion endpoint
  • Required access: Network access to the application; the necessary authentication state depends on deployment configuration
  • Trigger point: Processing of the ID argument by delete_exam.php
  • Why exploitation is possible: Authorization checks may not adequately bind the requested exam record to the requesting user's privileges

Why this happens

The underlying issue is an authorization-control failure in which a user-controlled object identifier is accepted without a reliable server-side permission check. This maps primarily to CWE-285: Improper Authorization and is also consistent with CWE-639: Authorization Bypass Through User-Controlled Key, where modifying an identifier can expose an operation on an object outside the caller's permitted scope.

Potential impact

  • An attacker may delete examination records without appropriate permission.
  • The application could lose assessment content or related administrative data.
  • Users may experience disruption to examination workflows.
  • The incident could undermine data integrity and administrative accountability.

General mitigation guidance

Mitigation generally focuses on enforcing authorization at the server-side operation boundary rather than trusting request parameters.

Common defensive patterns include:

  • Applying deny-by-default authorization checks before every deletion.
  • Verifying that the authenticated principal has permission for the specific exam object identified by the request.
  • Treating all object identifiers as untrusted and avoiding direct authorization decisions based solely on client-supplied values.
  • Using least-privilege roles and separating administrative deletion permissions from ordinary user capabilities.
  • Adding confirmation, audit logging, and soft-delete or recovery mechanisms where appropriate.
  • Returning consistent responses that do not disclose whether unauthorized objects exist.

How teams detect issues like this

Organizations can look for this weakness through:

  • Static analysis rules identifying destructive operations that use request parameters without nearby authorization checks.
  • Code review checks for direct database deletion based on user-controlled identifiers.
  • Tests that attempt access to objects owned by other users or roles with different permissions.
  • Monitoring for unusual deletion requests, repeated identifier changes, and destructive actions outside normal administrative patterns.
  • Policy enforcement requiring centralized authorization middleware or service-layer checks for sensitive operations.

Automated security review tools may help identify missing object-level authorization, but application-specific permission tests remain important.

Sources

SourceLink
github.comgithub.com/hackliu/Vulnerability-Reports/blob/master/Syllabus%20Aligned%20Learning%20Management%20Examination%20System/VULN-04-IDOR-Broken-Access-Control.md
vuldb.comvuldb.com/cve/CVE-2026-86277
vuldb.comvuldb.com/submit/904877
vuldb.comvuldb.com/vuln/399438
vuldb.comvuldb.com/vuln/399438/cti
sourcecodester.comsourcecodester.com/

Frequently asked

questions

Yes. The affected functionality is reachable through the application, although successful exploitation still depends on deployment exposure and any access controls around the endpoint.

The description does not establish a universal authentication requirement. The decisive factors are whether the endpoint is exposed and whether the attacker can obtain the application state needed to submit the request.

Enforce server-side, object-level authorization immediately before the deletion occurs, validating both the caller's role and access to the specific exam record.

Use centralized authorization policies, treat identifiers as untrusted input, test cross-user and cross-role access, and audit all destructive operations.

Find out what's already
exploitable in your codebase.