CVE-2026-11584
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 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.
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 · moderate confidenceSQL injection vulnerability in CodeAstro Student Attendance Management System 1.0 allows remote attackers to inject malicious SQL queries via the ID parameter in /attendance-php/Admin/createClass.php?action=edit. The application fails to properly sanitize user input before using it in database queries.
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.
-
Locate the application installationSearch for the 'attendance-php' directory in your web server's document root (commonly /var/www/html, /www, or C:\inetpub\wwwroot). Identify if the CodeAstro Student Attendance Management System is present.Affected if The attendance-php directory exists on the server and contains the application files.
-
Verify the application versionCheck for a version file or header within the attendance-php directory. Common locations include a version.txt, README file, or the main index.php header comments. Compare the found version to 1.0.Affected if The installed version is CodeAstro Student Attendance Management System 1.0.
-
Confirm the vulnerable script existsCheck if the file /attendance-php/Admin/createClass.php exists on the server. This is the vulnerable endpoint mentioned in the CVE.Affected if The file createClass.php exists in the /attendance-php/Admin/ directory.
-
Determine network exposureVerify if the attendance-php directory is accessible over the network (HTTP/HTTPS). Attempt to access the vulnerable endpoint URL: http(s)://<yourdomain>/attendance-php/Admin/createClass.php?action=edit&id=1Affected if The vulnerable endpoint is reachable from the network (not localhost-only or firewalled).
-
Review access logs for injection attemptsExamine web server access logs (access.log or error.log) for requests to createClass.php containing SQL injection patterns in the ID parameter, such as quotes, UNION SELECT, or boolean-based payloads.Affected if Log entries show SQL injection attempts targeting the ID parameter in createClass.php.
You are affected if the CodeAstro Student Attendance Management System version 1.0 is installed, the createClass.php file exists, and the vulnerable endpoint is network-accessible.
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 dataReplace dynamic SQL queries with parameterized queries/prepared statements. Implement proper input validation and sanitization on all user-controlled parameters before using them in database operations.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11584 — 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-11584 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