dbcve.org
Online Faculty Clearance SystemApplication · Fabian

CVE-2024-0462

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 was found in code-projects Online Faculty Clearance 1.0. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /production/designee_view_status.php of the component HTTP POST Request Handler. The manipulation of the argument haydi 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-250567.

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

A critical SQL injection vulnerability exists in the designee_view_status.php file of Online Faculty Clearance 1.0. The application fails to properly sanitize user input passed through the 'haydi' parameter in HTTP POST requests, allowing remote attackers to inject arbitrary SQL commands into the database query.

MitigationReplace dynamic SQL concatenation with prepared statements/parameterized queries for the 'haydi' parameter, implement strict input validation, and apply the vendor patch if available. Database accounts should use least-privilege principles.

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 Clearance 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 Fabian Online Faculty Clearance System installation
    Locate the web application's installation directory. Common paths include /var/www/html/ or C:\xampp\htdocs\ on Windows. Look for the main PHP files of the Fabian Online Faculty Clearance System.
    Affected if The Fabian Online Faculty Clearance System version 1.0 is installed on the server.
  2. Verify vulnerable file designee_view_status.php exists
    Navigate to the application directory and locate the file designee_view_status.php. This file handles the status view functionality and contains the vulnerable 'haydi' parameter handling.
    Affected if The file designee_view_status.php exists in the application installation.
  3. Inspect the 'haydi' POST parameter handling in the vulnerable file
    Open designee_view_status.php in a text editor and search for the 'haydi' parameter usage in $_POST or $_REQUEST. Examine how the parameter is incorporated into SQL queries - look for direct string concatenation or lack of prepared statements.
    Affected if The 'haydi' parameter from POST requests is used directly in SQL queries without parameterized queries or input sanitization.
  4. Check for SQL injection vulnerability
    Review the SQL query code in designee_view_status.php. Verify whether the 'haydi' parameter is passed directly into the query string without using prepare() or bindParam() methods, or any other form of input sanitization.
    Affected if The 'haydi' parameter is concatenated directly into SQL queries without prepared statements, allowing arbitrary SQL command injection.

A user is affected if the Fabian Online Faculty Clearance System version 1.0 is installed and the designee_view_status.php file processes the 'haydi' POST parameter without prepared statements or input sanitization.

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 dynamic SQL concatenation with prepared statements/parameterized queries for the 'haydi' parameter, implement strict input validation, and apply the vendor patch if available. Database accounts should use least-privilege principles.

Fix this in Online Faculty Clearance System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0462 — 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-0462 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