CVE-2022-2797
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 Student Information System. Affected by this vulnerability is an unknown functionality of the file /admin/students/view_student.php. The manipulation of the argument id leads to sql injection. The attack can be launched remotely. The identifier VDB-206245 was 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 · moderate confidenceA SQL injection vulnerability exists in SourceCodester Student Information System at /admin/students/view_student.php where the 'id' parameter is not properly sanitized before being used in SQL queries, allowing remote 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 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
- 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 Student Information System installationLocate the SourceCodester Student Information System web application files on the server. Common paths include /var/www/html/, /www/, or C:\inetpub\wwwroot\ depending on the operating system. Look for the view_student.php file within the /admin/students/ directory.Affected if The application is installed and the file structure matches SourceCodester Student Information System
-
Verify vulnerable file existsConfirm the presence of /admin/students/view_student.php in the web application directory. This is the specific file containing the SQL injection vulnerability.Affected if The file /admin/students/view_student.php exists in the web root
-
Check id parameter usage in SQL queriesExamine the source code of view_student.php and search for SQL queries that incorporate the 'id' parameter without proper sanitization or parameterized queries. Look for patterns like $_GET['id'] or $_POST['id'] directly concatenated into SQL statements.Affected if The 'id' parameter is used directly in SQL queries without prepared statements, escaping, or input validation
-
Determine network accessibilityVerify if the /admin/students/view_student.php endpoint is accessible over the network. Check firewall rules and web server configuration to confirm whether remote attackers can reach the affected URL.Affected if The vulnerable endpoint is accessible from untrusted network locations
-
Assess database user privilegesReview the database configuration used by the application. Check the database user credentials in the application configuration files to determine what privileges the application database account has.Affected if The database user has permissions beyond minimal read-only access (such as write, alter, or administrative privileges)
The environment is affected if the SourceCodester Student Information System is installed with the view_student.php file accessible over the network and the 'id' parameter is used directly in SQL queries without sanitization.
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 user input, particularly the 'id' parameter. Additionally, apply input validation and ensure database accounts run with least privilege.
- 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-2797 — 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-2797 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