CVE-2025-14646VulnerabilityPublished 14 Dec 2025Updated 15 Dec 2025

CVE-2025-14646: code-projects Student File Management System · SQL Injection

Affects code-projects Student File Management SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system 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 Vulnerable System.
Vulnerable system 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 to the Vulnerable System.
Vulnerable system 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 Vulnerable System 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 Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Dec 2025
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 Student File Management System	Affected =1.0	Fixed in–

AI-suggested

1. Immediately restrict access to the /admin/delete_student.php endpoint by IP whitelisting or VPN access to limit exposure. 2. Implement strict input validation and sanitization on the stud_id parameter to reject malicious payloads. 3. Refactor the application code to use parameterized queries or prepared statements to prevent SQL injection. 4. Monitor web server and database logs for suspicious activity related to the stud_id parameter or unusual SQL queries. 5. Deploy Web Application Firewalls (WAFs) with rules targeting SQL injection patterns to provide an additional layer of defense. 6. Conduct a thorough security audit of the entire Student File Management System to identify and remediate other potential injection points. 7. Engage with the vendor or community to obtain and apply official patches or updates as soon as they become available. 8. Educate administrators on the risks and signs of exploitation to enable rapid detection and response.

Description

A security flaw has been discovered in code-projects Student File Management System 1.0. This impacts an unknown function of the file /admin/delete_student.php. The manipulation of the argument stud_id results in sql injection. The attack may be performed from remote. The exploit has been released to the public and may be exploited.

Impact

For European organizations, especially educational institutions using the affected Student File Management System, this vulnerability poses a significant risk to the confidentiality and integrity of student data. Exploitation could lead to unauthorized disclosure of personal information, alteration or deletion of student records, and potential disruption of administrative operations. This could result in regulatory non-compliance, reputational damage, and operational downtime. Given the remote and unauthenticated nature of the exploit, attackers can target vulnerable systems from anywhere, increasing the attack surface. The public availability of exploit code further elevates the threat level. Organizations in Europe with limited cybersecurity resources or lacking timely patch management processes are particularly vulnerable. The impact extends beyond data loss to potential legal consequences under GDPR due to exposure of personal data.

Summary

CVE-2025-14646 is a SQL injection vulnerability identified in the Student File Management System version 1.0 developed by code-projects. The vulnerability resides in the /admin/delete_student.php script, specifically in the handling of the stud_id parameter. This parameter is vulnerable to SQL injection due to insufficient input validation or sanitization, allowing an attacker to inject malicious SQL statements remotely. The vulnerability can be exploited without any authentication or user interaction, making it accessible to unauthenticated remote attackers. Successful exploitation can lead to unauthorized data access, modification, or deletion within the backend database, impacting confidentiality, integrity, and availability of student records and potentially other sensitive data stored in the system. The vulnerability has a CVSS 4.0 base score of 6.9, indicating a medium severity level. The exploit code has been publicly released, increasing the likelihood of exploitation attempts. No patches are currently linked, so organizations must rely on interim mitigations such as input validation, use of prepared statements, and restricting access to the vulnerable administrative endpoint until an official fix is available.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Dec 2025, 07:13 UTC

Technical details

References

Community reviews

Related threats