dbcve.org
InjectionWeakness · CWE-74

CVE-2026-11583

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A vulnerability has been found in CodeAstro Student Attendance Management System 1.0. This affects an unknown function of the file /attendance-php/Admin/createClass.php. The manipulation of the argument className leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may 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 confidence

SQL injection vulnerability in CodeAstro Student Attendance Management System 1.0 allows remote attackers to inject malicious SQL queries via the className parameter in /attendance-php/Admin/createClass.php. The lack of input sanitization or parameterized queries enables arbitrary database manipulation.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in createClass.php, perform input validation on all user-supplied parameters, and conduct a broader code review to identify and remediate similar SQL injection vulnerabilities throughout the application.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the application installation
    Search for the 'attendance-php' directory or the 'createClass.php' file in your web server's document root. Common paths include /var/www/html/attendance-php/Admin/createClass.php or C:\inetpub\wwwroot\attendance-php\Admin\createClass.php
    Affected if The file /attendance-php/Admin/createClass.php exists on the server
  2. Confirm the application version
    Check for a version indicator in the application. Look for a README file, version.php, or admin dashboard footer that displays the software version. Compare against '1.0'
    Affected if The installed version is CodeAstro Student Attendance Management System 1.0
  3. Identify the vulnerable parameter usage
    Open createClass.php and search for occurrences of 'className' or $_POST/$_GET references that handle the className parameter. Verify the code directly uses this parameter in SQL queries without sanitization functions like mysqli_real_escape_string or prepared statements
    Affected if The className parameter is used in a SQL query without parameterized queries or input sanitization
  4. Check if the Admin panel is accessible
    Attempt to access /attendance-php/Admin/ login page to determine if the administrative interface is reachable. The vulnerability requires admin-level access to reach createClass.php
    Affected if The Admin panel is accessible and createClass.php can be reached via HTTP POST requests
  5. Verify the database configuration
    Examine the database connection file (commonly db.php or config.php in the attendance-php directory) to confirm the application uses dynamic SQL queries rather than prepared statements for class creation operations
    Affected if The application uses dynamic SQL construction for the createClass functionality

Your environment is affected if you are running CodeAstro Student Attendance Management System version 1.0 with the createClass.php file present and the className parameter processed through unsanitized dynamic SQL queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements in createClass.php, perform input validation on all user-supplied parameters, and conduct a broader code review to identify and remediate similar SQL injection vulnerabilities throughout the application.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11583 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11583 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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