College Management SystemApplication · College Management System Project

CVE-2022-39180

CRITICAL · 9.8 CVSS v3.1 Published 2022-11-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
College Management System v1.0 - SQL Injection (SQLi). By inserting SQL commands to the username and password fields in the login.php page

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 confidence

SQL injection vulnerability in the login.php page of College Management System v1.0 allows attackers to inject malicious SQL commands through the username and password fields, potentially enabling unauthorized authentication, data exfiltration, or database compromise.

MitigationReplace string concatenation in SQL queries with prepared statements/parameterized queries in login.php and audit all other user input handling for similar injection flaws.

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
College Management SystemApplication
Affected:= 1.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm College Management System v1.0 is installed
    Locate the College Management System installation directory and check for version identification files (such as version.php, README, or install manifest) that explicitly show version 1.0
    Affected if The installed version is College Management System version 1.0
  2. Verify login.php exists in the web root
    Check for the presence of login.php in the application's web-accessible directory, typically in the root folder of the College Management System installation
    Affected if login.php file exists in the application root
  3. Inspect SQL query implementation in login.php
    Open login.php in a text editor and locate the SQL query that handles username and password authentication. Look for SQL queries constructed using string concatenation (e.g., $sql = "SELECT * FROM users WHERE username='" . $username . "'") rather than prepared statements or parameterized queries
    Affected if The login.php file contains SQL queries built with string concatenation operators (dots or +) inserting user-supplied variables directly into the query string
  4. Confirm user input reaches the vulnerable query
    Trace the code flow from the username and password form input fields ($_POST['username'], $_POST['password']) to confirm they are passed to the unsanitized SQL query without proper escaping or use of parameterized queries
    Affected if Raw POST parameters from the login form are directly interpolated into SQL queries without escaping or parameter binding
  5. Verify the login page is accessible
    Attempt to access the login.php page via HTTP/HTTPS to confirm the authentication endpoint is reachable and the vulnerable code path can be executed
    Affected if The login.php page is accessible over the network and accepts user input

You are affected if College Management System v1.0 is installed, login.php exists, and its authentication SQL query uses string concatenation to incorporate user input rather than prepared statements.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace string concatenation in SQL queries with prepared statements/parameterized queries in login.php and audit all other user input handling for similar injection flaws.

Fix this in College Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-39180 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-39180 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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