CVE-2023-6658
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 classified as critical was found in SourceCodester Simple Student Attendance System 1.0. This vulnerability affects unknown code of the file ajax-api.php?action=save_attendance. The manipulation of the argument class_id leads to sql injection. The exploit has been disclosed to the public and may be used. VDB-247366 is the identifier assigned to this vulnerability.
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 · high confidenceSQL injection vulnerability in SourceCodester Simple Student Attendance System 1.0's ajax-api.php file. The class_id parameter in the save_attendance action is not properly sanitized, allowing attackers to inject malicious SQL queries. With a CVSS score of 9.8 and a publicly available exploit, this vulnerability can be exploited remotely without authentication to potentially extract, modify, or delete database contents.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify the application versionLocate the SourceCodester Simple Student Attendance System installation and check the version declaration in the source code, typically in a version.php file, README, or the main application header. Compare against version 1.0.Affected if The installed version is exactly 1.0 of Simple Student Attendance System by Oretnom23.
-
Locate the vulnerable ajax-api.php fileNavigate to the web root directory and search for the ajax-api.php file, commonly found in the includes or main application folder. Confirm its presence.Affected if The ajax-api.php file exists in the application directory.
-
Verify the save_attendance action existsOpen ajax-api.php and search for the 'save_attendance' case or action handler. Confirm the code processes this action.Affected if The save_attendance action is defined in ajax-api.php.
-
Inspect class_id parameter handlingWithin the save_attendance code block, locate where the class_id parameter is retrieved (typically via $_POST or $_GET) and used in SQL queries. Check if the value is directly concatenated into the query string without escaping, binding, or use of prepared statements.Affected if The class_id parameter is used directly in an SQL query without parameterized queries, escaping, or input validation.
You are affected if you are running Simple Student Attendance System version 1.0 and the ajax-api.php file contains the save_attendance action with unsanitized class_id parameter used in dynamic SQL queries.
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 in ajax-api.php, implement strict input validation on the class_id parameter, and apply the vendor patch if available. Consider deploying a WAF as a temporary compensating control.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6658 — 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-2023-6658 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