CVE-2026-11584
Received Received - Intake
SQL Injection in CodeAstro Student Attendance Management System

Publication date: 2026-06-08

Last updated on: 2026-06-08

Assigner: VulDB

Description
A vulnerability was found in CodeAstro Student Attendance Management System 1.0. This impacts an unknown function of the file /attendance-php/Admin/createClass.php?action=edit. The manipulation of the argument ID results in sql injection. It is possible to launch the attack remotely. The exploit has been made public and could be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-08
Last Modified
2026-06-08
Generated
2026-06-09
AI Q&A
2026-06-08
EPSS Evaluated
N/A
NVD
CVE-2026-11584
EUVD
EUVD-2026-35198
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
codeastro student_attendance_management_system 1.0
andelstander student_attendance_management_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
CWE-74 The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

The CVE-2026-11584 vulnerability affects the Student Attendance Management System version 1.0, specifically in the file /attendance-php/Admin/createClass.php when accessed with the parameters action=edit and Id=1.

This vulnerability is a SQL injection flaw caused by insufficient input validation of the Id parameter, which allows attackers to inject malicious SQL queries directly into the database.

An attacker can exploit this remotely, and a proof-of-concept demonstrates a time-based blind SQL injection where the database response can be delayed to confirm the vulnerability.

Compliance Impact

The SQL injection vulnerability in the Student Attendance Management System could lead to unauthorized database access, data tampering, and sensitive information leakage. Such impacts may result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive data against unauthorized access and breaches.

Exploitation of this vulnerability could compromise the confidentiality and integrity of stored data, potentially violating regulatory requirements for data security and privacy.

Impact Analysis

Exploitation of this vulnerability could lead to unauthorized access to the database, allowing attackers to tamper with data, leak sensitive information, gain control over the system, or disrupt services.

Detection Guidance

This vulnerability can be detected by testing the SQL injection flaw in the file `/attendance-php/Admin/createClass.php` with the parameters `action=edit` and `Id`.

A proof-of-concept involves a time-based blind SQL injection where the attacker forces the database to delay responses by five seconds, confirming the vulnerability.

To detect this, you can use commands or tools that send crafted requests to the vulnerable URL and observe response delays or errors indicating SQL injection.

  • Use curl to test for time delays: `curl "http://target/attendance-php/Admin/createClass.php?action=edit&Id=1 AND IF(SLEEP(5),1,0)"` and check if the response is delayed by about 5 seconds.
  • Use SQL injection detection tools like sqlmap targeting the URL with the vulnerable parameter: `sqlmap -u "http://target/attendance-php/Admin/createClass.php?action=edit&Id=1" --time-sec=5`.
Mitigation Strategies

Immediate mitigation steps include:

  • Implement prepared statements with parameter binding to prevent SQL injection.
  • Apply strict input validation on the `Id` parameter to ensure only expected values are accepted.
  • Minimize database user permissions to limit the impact of a potential exploit.
  • Conduct regular security audits and code reviews to identify and fix similar vulnerabilities.
Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-11584. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart