CVE-2025-14623VulnerabilityPublished 13 Dec 2025Updated 15 Dec 2025

CVE-2025-14623: 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 13 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

To mitigate CVE-2025-14623, organizations should immediately implement input validation and sanitization on the stud_id parameter to prevent injection of malicious SQL code. Employ parameterized queries or prepared statements in the /admin/update_student.php script to ensure user input is treated as data, not executable code. Restrict access to the /admin/update_student.php endpoint using network-level controls such as IP whitelisting or VPN access to limit exposure. Monitor web server and database logs for suspicious queries indicative of SQL injection attempts. If possible, upgrade to a patched version once available or apply vendor-provided security patches promptly. Conduct a thorough code review of the entire application to identify and remediate similar injection flaws. Implement Web Application Firewalls (WAFs) with rules tailored to detect and block SQL injection payloads targeting this system. Educate system administrators and developers on secure coding practices and the importance of timely patch management. Finally, ensure regular backups of student data are maintained and tested for restoration to mitigate data loss in case of compromise.

Description

A weakness has been identified in code-projects Student File Management System 1.0. This issue affects some unknown processing of the file /admin/update_student.php. This manipulation of the argument stud_id causes sql injection. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be exploited.

Impact

For European organizations, particularly educational institutions using the affected Student File Management System version 1.0, this vulnerability poses significant risks. Exploitation could lead to unauthorized disclosure of student personal information, violating GDPR and other data protection regulations, resulting in legal and financial penalties. Integrity of student records could be compromised, affecting academic outcomes and institutional trust. Availability of the system might be disrupted if attackers execute destructive SQL commands, impacting administrative operations. The medium severity rating indicates a moderate but tangible threat, especially given the public availability of exploit code and the lack of authentication required for exploitation. Institutions with limited cybersecurity resources or outdated software maintenance practices are particularly vulnerable. The reputational damage from a breach involving student data could be substantial. Additionally, attackers could leverage this access as a foothold for further network intrusion. The impact is amplified in countries with higher adoption of this software or where educational data is a strategic target for cyber espionage or ransomware campaigns.

Summary

CVE-2025-14623 identifies a SQL injection vulnerability in the Student File Management System version 1.0 developed by code-projects. The vulnerability arises from insufficient input validation of the stud_id parameter in the /admin/update_student.php script. This allows an unauthenticated remote attacker to inject malicious SQL statements directly into the backend database queries. The vulnerability is exploitable over the network without any user interaction or privileges, making it highly accessible for attackers. The SQL injection can be leveraged to read sensitive student data, modify records, or even execute administrative commands on the database server, potentially leading to data breaches or system compromise. The CVSS 4.0 score of 6.9 reflects a medium severity, considering the lack of authentication and user interaction but limited scope and impact compared to more critical vulnerabilities. No official patches have been published yet, and while no active exploitation has been reported, public exploit code availability increases the risk. The vulnerability affects only version 1.0 of the software, which may still be in use in some educational institutions. The absence of secure coding practices such as parameterized queries or prepared statements is the root cause. This flaw highlights the importance of rigorous input sanitization and secure development lifecycle adherence in educational software handling sensitive personal data.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Dec 2025, 20:06 UTC

Technical details

References

Community reviews

Related threats