CVE-2023-1099
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 SourceCodester Online Student Management System 1.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file eduauth/edit-class-detail.php. The manipulation of the argument editid leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. VDB-222002 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 Online Student Management System 1.0's eduauth/edit-class-detail.php file. The 'editid' parameter is directly incorporated into SQL queries without proper sanitization or parameterized queries, allowing remote attackers to manipulate SQL statements and potentially access, 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.
-
Confirm the application versionIdentify if the deployed system is SourceCodester Online Student Management System version 1.0 by checking application files, headers, or documentationAffected if The installed version is Online Student Management System 1.0 from SourceCodesters
-
Locate the vulnerable scriptSearch for the file eduauth/edit-class-detail.php in the web application directory structureAffected if The file eduauth/edit-class-detail.php exists in the deployed application
-
Inspect SQL query implementationOpen eduauth/edit-class-detail.php and examine how the 'editid' parameter is used in SQL queries - look for whether the code uses prepared statements, parameter binding, or direct string concatenationAffected if The 'editid' parameter is incorporated into SQL queries without prepared statements or parameter binding (e.g., using $_GET['editid'] directly in SQL string)
-
Verify database user privilegesCheck the database configuration to determine what privileges the application database user hasAffected if The database user has elevated privileges that could allow exploitation to read/modify/delete data
-
Assess network accessibilityDetermine if the affected PHP file is accessible over the network (HTTP/HTTPS)Affected if The eduauth/edit-class-detail.php endpoint is reachable via HTTP/HTTPS to an attacker
The environment is affected if running SourceCodester Online Student Management System 1.0 with the eduauth/edit-class-detail.php file present and the editid parameter used in unsanitized 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 query construction with prepared statements/parameterized queries for the editid parameter. Apply input validation and ensure all database interactions use PDO or mysqli with bound parameters.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1099 — 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-1099 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