CVE-2026-11585
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 determined in CodeAstro Student Attendance Management System 1.0. Affected is an unknown function of the file /attendance-php/Admin/createClassArms.php. This manipulation of the argument classId causes sql injection. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized.
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 confidenceCodeAstro Student Attendance Management System 1.0 contains a SQL injection vulnerability in /attendance-php/Admin/createClassArms.php via the classId parameter. An attacker can manipulate this input to inject arbitrary SQL queries, potentially allowing unauthorized data access, modification, or database compromise.
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.
-
Confirm CodeAstro Student Attendance Management System is installedSearch for the 'attendance-php' directory or the specific file /attendance-php/Admin/createClassArms.php on the web server filesystemAffected if The application directory structure matches the path /attendance-php/Admin/createClassArms.php
-
Identify the installed versionCheck version.php, version.txt, or any version file in the application root, or examine HTTP headers/banners from the applicationAffected if The version is 1.0 or cannot be determined (assume affected if the vulnerable file exists)
-
Verify the vulnerable endpoint is accessibleAttempt to access the URL path /attendance-php/Admin/createClassArms.php via HTTP/HTTPS request and confirm the application respondsAffected if The endpoint returns a valid HTTP response (200, 302, etc.) rather than a 404 error
-
Check if the classId parameter is processed without sanitizationExamine the source code of createClassArms.php and search for SQL queries that incorporate the classId parameter directly, noting whether prepared statements or parameter binding is usedAffected if The code contains SQL queries with classId concatenated directly into the query string without using prepared statements or escaping functions
The environment is affected if CodeAstro Student Attendance Management System 1.0 is installed with the /attendance-php/Admin/createClassArms.php endpoint accessible and the classId parameter processed in SQL queries without parameterized statements.
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 dataImplement prepared statements/parameterized queries for all database operations involving the classId parameter in createClassArms.php, and conduct a comprehensive code audit to identify and remediate similar injection vulnerabilities throughout the application.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11585 — 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-11585 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