CVE-2026-9484
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 · uneditedA vulnerability was determined in SourceCodester Student Grades Management System 1.0. Affected by this vulnerability is the function getClassroomStudents/removeStudentFromClassroom of the file classroom.php. Executing a manipulation of the argument classroom_id can lead to improper authorization. The attack may be launched remotely. The exploit has been publicly disclosed and may be utilized.
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 · high confidenceThe Student Grades Management System 1.0 contains an improper authorization vulnerability in classroom.php where the functions getClassroomStudents and removeStudentFromClassroom fail to validate user authorization when processing the classroom_id parameter. An attacker can manipulate this argument to access or modify classroom data they should not have permission to view or modify.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Student Grades Management System installationLocate the web application files and check for classroom.php in the application directory structure. Verify the application is version 1.0 by checking any version file, about page, or metadata.Affected if The application is running and classroom.php exists with version 1.0
-
Identify the vulnerable classroom.php fileNavigate to the application root directory and locate classroom.php. Open the file and search for the getClassroomStudents and removeStudentFromClassroom function definitions.Affected if The file classroom.php exists and contains these two functions
-
Verify getClassroomStudents lacks authorization checksExamine the getClassroomStudents function in classroom.php. Look for code that retrieves classroom data using the classroom_id parameter WITHOUT first validating that the current user owns or has permission to access that classroom (e.g., no check like 'WHERE user_id = current_user' or session validation).Affected if The function directly queries classroom data using classroom_id without ownership/permission validation
-
Verify removeStudentFromClassroom lacks authorization checksExamine the removeStudentFromClassroom function in classroom.php. Check if the function uses the classroom_id parameter to remove students WITHOUT verifying the authenticated user has permission to modify that specific classroom.Affected if The function modifies classroom data without validating user permissions on the referenced classroom_id
-
Check for user session or ownership validationSearch the classroom.php file for session validation, user ID comparison, or ownership queries that would restrict classroom access to only authorized users. Look for patterns like 'WHERE classroom_id = ? AND user_id = ?' or similar authorization logic.Affected if No such authorization logic exists before accessing or modifying classroom data based on the classroom_id parameter
-
Test the IDOR vulnerability manuallyLog into the application with a standard user account. Access classroom.php with a classroom_id that belongs to a different user or classroom you do not own. For getClassroomStudents, observe if you receive data for an unauthorized classroom. For removeStudentFromClassroom, attempt to remove a student from an unauthorized classroom.Affected if You can access or modify classroom data for classroom_ids you do not own or have not been assigned to
Your environment is affected if Student Grades Management System 1.0 is running with classroom.php present and the application allows access or modification of classroom data via classroom_id without verifying user ownership or permissions.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement server-side authorization checks to verify the authenticated user has appropriate permissions for the requested classroom_id before returning data or performing removal operations. Use role-based access control and validate user-classroom associations.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9484 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-9484 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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