Severity:

HIGH RISK

(7.3)

Improper Access Control in CodeIgniter Student Management

CVE-2026-9517

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-266, CWE-284

Impact:

Unauthorized Access and Data Manipulation

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

An improper access control vulnerability in the Student Management Handler of the CodeIgniter-StudentManagementSystem exposes the /index.php/students/addStudentView endpoint to unauthorized use.

Under certain conditions, a remote attacker may be able to access or invoke student management functionality without appropriate permissions, potentially leading to unauthorized data access or changes.

Affected context

This issue appears in the Student Management Handler, specifically around the /index.php/students/addStudentView path.

It typically surfaces where role- or permission-based checks are missing, incomplete, or inconsistently enforced on controller actions that handle student creation or management.

The risk is most pronounced in deployments exposed to the internet where authentication and authorization controls are not strictly validated before serving this view or processing related actions.

Exploit preconditions

  • Attack surface: HTTP interface of the Student Management System
  • Required access: Network access to the web application; no valid user account may be required if authorization is missing or weak
  • Trigger point: Direct or indirect invocation of /index.php/students/addStudentView or related routes handling student management
  • Why exploitation is possible: Authorization checks on the targeted controller or function are absent, incomplete, or bypassable, allowing an attacker to reach privileged functionality intended only for authenticated or higher-privilege users

Why this happens

The underlying flaw aligns with CWE-284: Improper Access Control and CWE-266: Incorrect Privilege Assignment, where the application fails to correctly enforce which users can reach a sensitive handler.

In practical terms, the controller action responsible for presenting or processing the add-student view likely does not verify the current user's authentication status, role, or specific permissions, or does so inconsistently.

This insecure pattern allows untrusted callers to perform operations or access data that should be restricted to trusted roles, such as administrators or staff, thereby weakening the intended privilege model of the system.

Potential impact

  • Unauthorized viewing of student-related information or forms
  • Creation or modification of student records by unprivileged users
  • Exposure of internal workflow details that can aid further attacks
  • Escalation of privileges if chained with other weaknesses in the system
  • Potential data integrity issues in student management records

General mitigation guidance

Mitigation generally centers on enforcing consistent, centralized authorization checks for all sensitive handlers and routes.

Useful patterns include:

  • Applying role-based access control (RBAC) or similar schemes to every controller method that manipulates student data
  • Using framework-level middleware or filters to require authentication and specific roles before dispatching to actions like addStudentView
  • Designing least-privilege roles so that only necessary operations are exposed to each class of user
  • Normalizing authorization logic in a shared component rather than duplicating checks across multiple controllers
  • Logging authorization decisions to support ongoing review and refinement of access rules

How teams detect issues like this

Detection typically combines code- and behavior-oriented approaches:

  • Static analysis and code review: Look for controller methods that handle student management without explicit authentication/authorization checks or middleware; search for routes that return protected views without verifying user context.
  • Access control matrix review: Compare implemented route protections against a documented matrix of which roles should access what functions.
  • Dynamic testing: Attempt to reach /index.php/students/addStudentView and similar endpoints without logging in, or while logged in as a low-privilege user, to confirm enforcement.
  • Policy enforcement tools: Employ application security scanners or automated review tools that flag unprotected endpoints under sensitive controllers.

Sources

SourceLink
github.comgithub.com/hemant6488/CodeIgniter-StudentManagementSystem/
github.comgithub.com/hemant6488/CodeIgniter-StudentManagementSystem/issues/5
vuldb.comvuldb.com/submit/814277
vuldb.comvuldb.com/vuln/365537
vuldb.comvuldb.com/vuln/365537/cti

Frequently asked

questions

Yes. As described, the attack can be executed remotely by anyone with network access to the web application, assuming the vulnerable endpoint is reachable.

In many improper access control scenarios, no valid account is required; an unauthenticated or low-privilege user may exploit the weakness if the route lacks proper authorization checks. The exact requirement depends on how the deployment is configured.

The most robust fix is to enforce centralized, role-aware authorization for all student management handlers, ensuring that sensitive routes like addStudentView can only be accessed by authenticated users with explicit permissions (e.g., administrator or staff roles). Applying consistent middleware or filters at the controller or module level helps avoid gaps.

Establish a clear access control policy, map it to an access control matrix, and use framework features (such as middleware, guards, or filters) to enforce it uniformly. Incorporate security-focused code review, automated checks for unprotected routes, and regular testing of authorization rules into the development lifecycle.

Find out what's already
exploitable in your codebase.