Quick answers
- Is CVE-2026-82553 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82553 being exploited in the wild.
- How severe is CVE-2026-82553?
- Medium severity, with a CVSS score of 6.3, published 30 August 2026.
- Which products and versions are affected?
- Sambitraj Student Management System up to commit 56ba287f2e9031523ccb4244cb6e3fe530e4e5d5.
- Is there a fix for CVE-2026-82553?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-82553 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-82553?
- Check whether you run Sambitraj Student Management System at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an Insecure Direct Object Reference (IDOR) authorization bypass in the student_dashboard.php component. The vulnerable code accepts a user-supplied roll_no parameter in a POST request and queries the database without verifying that the authenticated student owns the requested record. The mysqli_query function executes an unauthenticated SQL query based on the roll_no parameter, returning sensitive fields (email, password, remarks, grades) to any logged-in student regardless of record ownership. No row-level access control or session-based ownership validation is performed. An attacker with valid student credentials can exploit this over the network by modifying the roll_no parameter to enumerate and retrieve other students' data. The product uses a rolling release model and has not yet responded to the disclosure.
Affected products
- sambitraj Student Management System up to commit 56ba287f2e9031523ccb4244cb6e3fe530e4e5d5
Timeline
- 2026-08-30: disclosed: CVE-2026-82553 published
- 2026-07-15: other: Issue reported on GitHub