Description

A vulnerability was detected in sambitraj Student-Management-System up to 56ba287f2e9031523ccb4244cb6e3fe530e4e5d5. Affected by this issue is some unknown functionality of the component Dashboard. The manipulation of the argument roll_no/teacher_name results in sql injection. The attack can be executed remotely. The exploit is now public and may be used. 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.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "6.3",
  "pubDate": "2026-08-23T03:16:59.777Z",
  "pubdate": "2026-08-23T03:16:59.777Z",
  "executiveSummary": "A critical SQL injection vulnerability has been identified within the Dashboard component of sambitraj Student-Management-System up to commit 56ba287f2e9031523ccb4244cb6e3fe530e4e5d5.\nThe vulnerability arises from the insecure handling of user-supplied input passed via the roll_no or teacher_name arguments.\nAn unauthenticated or remote attacker can manipulate these parameters to inject malicious SQL commands directly into database queries executed by the application.\nSuccessful exploitation of this flaw can lead to unauthorized access, data exfiltration, modification, or complete compromise of the underlying database infrastructure.\nThe risk is elevated due to the public availability of exploits targeting this flaw and the lack of a vendor response or official patch, as the product utilizes a rolling release model without explicit version numbers.",
  "technicalDetails": "The vulnerability stems from improper neutralization of special elements used in an SQL command within the Dashboard component of sambitraj Student-Management-System.\nSpecifically, the application accepts input through the roll_no and teacher_name parameters and dynamically concatenates or interpolates this input directly into backend SQL queries without adequate parameterization, input sanitization, or type enforcement.\nThe attack flow begins when a remote adversary interacts with the vulnerable Dashboard functionality over the network.\nThe attacker crafts a malicious HTTP request containing SQL syntax within the vulnerable roll_no or teacher_name arguments.\nBecause the input lacks parameterized queries or prepared statements, the database query interpreter parses the injected payload as executable SQL code rather than literal data.\nThis allows the attacker to alter the logic of the database query, bypass authentication mechanisms, extract sensitive records from the database schema, or execute administrative operations depending on the database user privileges.\nThe affected codebase encompasses revisions up to commit 56ba287f2e9031523ccb4244cb6e3fe530e4e5d5, utilizing a rolling release delivery model.\nSince public exploit code is actively available, threat actors can automate the injection process to compromise vulnerable instances reachable over the network."
}