CVE-2024-0464VulnerabilityPublished 12 Jan 2024Updated 3 Jun 2025

CVE-2024-0464: code-projects Online Faculty Clearance · SQL Injection

Affects code-projects Online Faculty ClearanceSource CVE Database V5

Not known to be exploited · CVSS 6.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
code-projects Online Faculty Clearance	Affected =1.0	Fixed in–

AI-suggested

European organizations should immediately conduct an inventory to identify any deployments of code-projects Online Faculty Clearance version 1.0. Until a vendor patch is available, organizations should implement the following specific mitigations: 1) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the 'id' parameter in delete_faculty.php. 2) Restrict access to the clearance system to trusted IP ranges or via VPN to reduce exposure. 3) Conduct code reviews and apply manual input validation and parameterized queries or prepared statements in the delete_faculty.php script to sanitize the 'id' parameter, if source code access is possible. 4) Monitor logs for unusual database query patterns or repeated failed attempts to manipulate the 'id' parameter. 5) Implement database-level restrictions such as least privilege for the application database user to limit the impact of any injection. 6) Prepare incident response plans for potential data breaches or service disruptions related to this vulnerability. Organizations should also engage with the vendor or community to obtain patches or updates and apply them promptly once available.

Description

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.

Impact

For European organizations, particularly educational institutions using the Online Faculty Clearance system version 1.0, this vulnerability poses a significant risk. Exploitation could lead to unauthorized access to faculty records, including personal and professional information, potentially violating GDPR and other data protection regulations. Data integrity could be compromised by unauthorized deletion or modification of faculty clearance records, disrupting administrative workflows and causing operational delays. Availability of the clearance system could also be affected if attackers execute destructive SQL commands, leading to denial of service. The medium CVSS score suggests moderate impact, but the critical nature of academic data and regulatory compliance in Europe elevates the practical impact. Additionally, the remote exploitability without user interaction means attackers can automate attacks, increasing the likelihood of widespread exploitation if the system remains unpatched. The lack of known exploits in the wild currently limits immediate risk, but public disclosure increases the urgency for mitigation.

Summary

CVE-2024-0464 is a SQL Injection vulnerability identified in version 1.0 of the code-projects Online Faculty Clearance application. The vulnerability exists in the delete_faculty.php script, specifically in the handling of the HTTP GET parameter 'id'. An attacker can manipulate this parameter to inject malicious SQL code, potentially altering the intended SQL query executed by the backend database. This type of injection can lead to unauthorized data access, modification, or deletion, impacting the confidentiality, integrity, and availability of the database. The vulnerability is remotely exploitable without user interaction, requiring only low privileges (PR:L) on the system, which suggests that an attacker with limited access could leverage this flaw. The CVSS 3.1 base score is 6.3, categorized as medium severity, reflecting the potential for limited impact on confidentiality, integrity, and availability. No public exploits are currently known in the wild, but the vulnerability details have been disclosed publicly, increasing the risk of exploitation. The absence of available patches or mitigations from the vendor further elevates the threat level for users of this specific application version. The CWE-89 classification confirms this is a classic SQL Injection issue, a well-understood and critical web application security risk. Given the nature of the affected software—an online faculty clearance system—successful exploitation could disrupt academic administrative processes and expose sensitive faculty data.

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Jul 2025, 15:10 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats