dbcve.org
Online Faculty Clearance SystemApplication · Fabian

CVE-2024-0461

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 classified as critical. Affected is an unknown function of the file deactivate.php of the component HTTP POST Request Handler. The manipulation of the argument haydi leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. VDB-250566 is the identifier 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 the HTTP POST request handler of deactivate.php in Online Faculty Clearance 1.0. The 'haydi' parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL code.

MitigationImplement prepared statements/parameterized queries for all SQL operations in deactivate.php, particularly for the 'haydi' parameter. Input validation and escaping should also be applied as defense-in-depth.

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. Identify installed version of Fabian Online Faculty Clearance System
    Check the application version by inspecting source files, README, or any version metadata in the web root directory. Common paths: /var/www/html/ or C:\inetpub\wwwroot\
    Affected if The installed version is 1.0 and the application is deployed
  2. Locate deactivate.php in the web application directory
    Search for deactivate.php in the application's web-accessible directories. Common patterns: /admin/deactivate.php, /php/deactivate.php, or in the root directory
    Affected if deactivate.php exists and is accessible via the web server
  3. Inspect the 'haydi' parameter handling in deactivate.php
    Open deactivate.php and examine the code that handles the 'haydi' POST parameter. Look for direct use of $_POST['haydi'] in SQL queries without prepare() statements or parameter binding
    Affected if The code uses $_POST['haydi'] directly in SQL queries without parameterized queries or input sanitization
  4. Check if the web server can process POST requests to deactivate.php
    Send a test HTTP POST request to deactivate.php with the 'haydi' parameter. Use a tool like curl: curl -X POST -d 'haydi=test' http://TARGET/deactivate.php
    Affected if The endpoint accepts POST requests and processes the 'haydi' parameter
  5. Verify SQL query construction in deactivate.php
    Examine all SQL query strings in deactivate.php. Look for concatenation or string interpolation of the 'haydi' variable into query strings. Search for patterns like $sql = "..." . $_POST['haydi']
    Affected if The 'haydi' parameter is concatenated directly into SQL query strings without escaping or parameterization

The environment is affected if Fabian Online Faculty Clearance System version 1.0 is deployed and deactivate.php processes the 'haydi' POST parameter without using prepared statements or input sanitization in its SQL queries.

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

Implement prepared statements/parameterized queries for all SQL operations in deactivate.php, particularly for the 'haydi' parameter. Input validation and escaping should also be applied as defense-in-depth.

Fix this in Online Faculty Clearance System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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