Quick answers
- Is CVE-2026-78057 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78057 being exploited in the wild.
- How severe is CVE-2026-78057?
- Medium severity, with a CVSS score of 6.3, published 23 August 2026.
- Which products and versions are affected?
- Sambitraj Student Management System up to commit 56ba287f2e9031523ccb4244cb6e3fe530e4e5d5.
- Is there a fix for CVE-2026-78057?
- 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-78057 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-78057?
- 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 a classic SQL injection affecting the Management Mutation Handler component in add/edit/delete operations (add_student.php, add_teacher.php, add_result.php, admin_edit_student.php, admin_edit_teacher.php, admin_edit_result.php, delete_student.php, delete_teacher.php, delete_result.php). POST parameters including roll_no, name, father_name, class, mobile, email, password, and remark are directly embedded into SQL queries without parameterization or type casting. An unauthenticated attacker can craft POST requests with SQL predicates in parameters like "roll_no=1 OR 1=1" to modify all records instead of a single target, or use DELETE predicates to destroy data. The attack requires network access and does not mandate prior authentication; a published exploit exists and the vendor has not yet responded to the security report.
Affected products
- sambitraj Student Management System up to commit 56ba287f2e9031523ccb4244cb6e3fe530e4e5d5
Timeline
- 2026-08-23: disclosed: CVE-2026-78057 published on NVD
- 2026-07-06: other: Vulnerability reported via GitHub issue #5; vendor has not responded