CVE-2023-6771
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, which was classified as critical, has been found in SourceCodester Simple Student Attendance System 1.0. This issue affects the function save_attendance of the file actions.class.php. The manipulation of the argument sid leads to sql injection. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-247907.
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 the save_attendance function of actions.class.php in SourceCodester Simple Student Attendance System 1.0. The 'sid' parameter is not properly sanitized before being used in SQL queries, allowing attackers to inject malicious SQL code.
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.
-
Locate the application installationSearch for the Simple Student Attendance System by checking web server document roots, common paths like /var/www/html/, /opt/lampp/htdocs/, C:\xampp\htdocs\, or look for a folder containing 'actions.class.php'Affected if The application is found on the system at any accessible location
-
Verify the exact versionCheck the version number of the installed Oretnom23 Simple Student Attendance System by looking at README files, version.php, or the application itselfAffected if The installed version is exactly 1.0 (or the version cannot be determined but the application matches this product)
-
Locate the vulnerable fileFind actions.class.php in the application directory - typically in a /classes/ or /action/ folder within the attendance systemAffected if actions.class.php exists in the application
-
Inspect the save_attendance functionOpen actions.class.php and search for the 'save_attendance' function definition. Look for the handling of the 'sid' parameter within this functionAffected if The save_attendance function exists and handles a 'sid' parameter directly in SQL queries without visible sanitization
-
Check if the application is accessibleIf this is a web application, verify the application is accessible via browser or curl request to confirm it is runningAffected if The application is actively serving requests, making the SQL injection exploitable
The system is affected if Oretnom23 Simple Student Attendance System version 1.0 is installed and the actions.class.php file with the vulnerable save_attendance function handling the sid parameter is present and 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 and implement proper input validation on the sid parameter to prevent SQL injection attacks.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6771 — 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-6771 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