CVE-2022-2665
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 E-Learning System. Affected by this vulnerability is an unknown functionality of the file classroom.php. The manipulation of the argument post_id leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-205615.
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 confidenceA SQL injection vulnerability exists in SourceCodester Simple E-Learning System's classroom.php file. The post_id parameter is not properly sanitized, allowing remote attackers to inject malicious SQL queries. With a CVSS score of 8.8 (HIGH), this vulnerability could allow attackers to view, 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 dataall versionsCVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 vulnerable classroom.php fileSearch for the file 'classroom.php' in the web application's source code directory. Common paths may include /classes/ or the application root directory.Affected if The file classroom.php exists in the application and handles POST requests with a post_id parameter.
-
Verify the post_id parameter is in useInspect the classroom.php file and look for $_POST['post_id'] or $_REQUEST['post_id'] to confirm the parameter is being processed.Affected if The application processes a post_id parameter from user input without proper validation.
-
Check for unsanitized SQL query constructionExamine the classroom.php file for SQL queries that concatenate or embed the post_id variable directly into the query string without using prepared statements or parameter binding.Affected if SQL queries involving post_id are built using string concatenation or interpolation rather than parameterized queries.
-
Confirm database interaction with post_idReview the code flow in classroom.php to verify that the post_id value is passed to a database query function (such as mysqli_query, $conn->query, or similar).Affected if The post_id parameter flows directly into a database query without sanitization.
A user is affected if their Simple E-Learning System deployment contains the classroom.php file that processes a post_id parameter through 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 dataImplement parameterized queries (prepared statements) for all database operations involving the post_id parameter in classroom.php. Validate and sanitize all user inputs before using them in SQL queries.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2665 — 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-2022-2665 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