dbcve.org
Online Faculty ClearanceApplication · Code Projects

CVE-2024-0464

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-12
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
A vulnerability classified as critical has been found in code-projects Online Faculty Clearance 1.0. This affects an unknown part of the file delete_faculty.php of the component HTTP GET Request Handler. The manipulation of the argument id leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-250569 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 · high confidence

SQL injection vulnerability in delete_faculty.php of Online Faculty Clearance 1.0. The id parameter in a GET request is not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL commands. This critical vulnerability (CVSS 9.8) can lead to complete database compromise, including unauthorized data access, modification, or deletion.

MitigationReplace direct SQL query construction with parameterized queries (prepared statements) for the id parameter in delete_faculty.php. Implement input validation and apply the principle of least privilege to the database user account. Conduct a comprehensive audit of other PHP files for similar SQL injection vulnerabilities.

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
Online Faculty ClearanceApplication
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. Identify the installed version of Online Faculty Clearance
    Check your web application directory for version indicators such as a version.php file, readme.txt, or metadata in the main index.php. Compare the found version against the affected range (version 1.0).
    Affected if The installed version is Code Projects Online Faculty Clearance version 1.0
  2. Locate the delete_faculty.php file
    Search your web server document root for the file delete_faculty.php. Common paths may include /admin/, /php/, or the application root directory.
    Affected if The file delete_faculty.php exists in your installation
  3. Examine the id parameter handling in delete_faculty.php
    Open delete_faculty.php in a text editor and search for code that uses $_GET['id'] or $_REQUEST['id']. Look for SQL query construction where this parameter is concatenated directly into the query string without sanitization functions like mysqli_real_escape_string, htmlspecialchars, or type casting.
    Affected if The file contains $_GET['id'] or $_REQUEST['id'] used directly in SQL queries without prepared statements or parameter binding
  4. Check if the application uses prepared statements for database queries
    In delete_faculty.php, verify whether database queries use mysqli_prepare(), PDO::prepare(), or similar parameterized query methods. Search for patterns like $stmt = $mysqli->prepare() or $pdo->prepare().
    Affected if The code does NOT use prepared statements and instead constructs SQL queries by string concatenation with the id parameter

You are affected if you are running Online Faculty Clearance version 1.0 and the delete_faculty.php file contains unsanitized SQL queries using the id parameter from GET requests.

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 direct SQL query construction with parameterized queries (prepared statements) for the id parameter in delete_faculty.php. Implement input validation and apply the principle of least privilege to the database user account. Conduct a comprehensive audit of other PHP files for similar SQL injection vulnerabilities.

Fix this in Online Faculty Clearance Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing3.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0464 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2024-0464 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