dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-9517

HIGH · 7.3 CVSS v3.1 Published 2026-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was determined in hemant6488 CodeIgniter-StudentManagementSystem. The affected element is an unknown function of the file /index.php/students/addStudentView of the component Student Management Handler. Executing a manipulation can lead to improper access controls. The attack can be executed remotely. The exploit has been publicly disclosed and may be utilized. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. The project was informed of the problem early through an issue report but has not responded yet.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The CodeIgniter-StudentManagementSystem contains an improper access control vulnerability in the /index.php/students/addStudentView endpoint. The student management handler fails to properly enforce authorization checks when adding new student records, potentially allowing unauthorized users to create student entries. This is a remote, publicly disclosed vulnerability with a CVSS 7.3 severity rating.

MitigationImplement proper role-based access control (RBAC) checks in the addStudentView function to verify user permissions before allowing student creation. Review all student management endpoints for similar access control gaps and ensure authentication is properly enforced across the application.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if CodeIgniter Student Management System is deployed
    Check for the presence of CodeIgniter framework files (system/application folders) and look for student management application files - typically found in web root directories serving PHP applications
    Affected if The application is the CodeIgniter-based Student Management System
  2. Verify if the addStudentView endpoint exists
    Attempt to access or inspect the route /index.php/students/addStudentView - check if the file application/controllers/students.php (or similar path) contains an addStudentView function
    Affected if The addStudentView function exists in the students controller
  3. Test endpoint accessibility without authentication
    Send an HTTP GET or POST request to /index.php/students/addStudentView using a browser or curl tool without providing any session cookie, login credentials, or authentication token
    Affected if The endpoint returns a functional page or form rather than redirecting to a login page or returning a 401/403 error
  4. Inspect the controller for authorization checks
    Examine the students.php controller file - look for code that checks session validity, user role, or permission before executing the addStudentView function (e.g., $this->session->userdata('is_logged_in') or similar role checks)
    Affected if No session validation or role check code is present before the addStudentView functionality
  5. Check for missing route-level access controls
    Inspect CodeIgniter routes configuration (application/config/routes.php) and any filters/hooks defined for authentication - verify whether filters are defined and applied to the students controller routes
    Affected if No authentication filter or before_hook is configured for the addStudentView route

If the CodeIgniter Student Management System is deployed and the addStudentView endpoint is accessible without authentication or proper role verification, the environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper role-based access control (RBAC) checks in the addStudentView function to verify user permissions before allowing student creation. Review all student management endpoints for similar access control gaps and ensure authentication is properly enforced across the application.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9517 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9517 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data