CVE-2026-6167
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 detected in code-projects Faculty Management System 1.0. Impacted is an unknown function of the file /subject-print.php. The manipulation of the argument ID results in sql injection. The attack may be launched remotely. The exploit is now public and may be used.
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 Faculty Management System 1.0 allows remote attackers to inject malicious SQL queries via the ID parameter in /subject-print.php, potentially enabling unauthorized database access, data exfiltration, or manipulation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 Faculty Management System installationLocate the web application's root directory and verify the presence of Faculty Management System files, typically in the web server's document root (e.g., /var/www/html or C:\inetpub\wwwroot). Look for application files or check the HTTP banner if available.Affected if Faculty Management System 1.0 is installed and running on the server.
-
Locate subject-print.php fileSearch for the file subject-print.php within the web application's directory structure, commonly found in the root or admin/includes folders. Verify its presence via file system search or HTTP request to /subject-print.php.Affected if The file subject-print.php exists and is accessible via the web server.
-
Inspect ID parameter handling in subject-print.phpOpen subject-print.php and examine the code handling the 'ID' parameter. Look for SQL queries that incorporate the ID parameter directly without using prepared statements, parameter binding, or input sanitization. Search for patterns like $_GET['ID'], $_POST['ID'], or Request::get('ID') used in concatenated SQL strings.Affected if The ID parameter is used in SQL queries without parameterized binding or proper input validation, indicating the SQL injection vulnerability is present.
-
Verify database query executionConfirm the application connects to a database and executes the SQL queries containing the ID parameter. Check if the code passes the unsanitized ID value directly to database execution functions like mysqli_query(), mysql_query(), or PDO::query().Affected if The application executes SQL queries with unsanitized ID parameter values against the database.
The environment is affected if Faculty Management System 1.0 is installed, subject-print.php is accessible, and the ID parameter in that file is handled in SQL queries without prepared statements or input 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 dataReplace dynamic SQL queries with prepared statements/parameterized queries for the ID parameter in subject-print.php and implement strict input validation. Review other files for similar injection vulnerabilities.
- 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-2026-6167 — 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-2026-6167 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