CVE-2025-14578VulnerabilityPublished 12 Dec 2025Updated 15 Dec 2025

CVE-2025-14578: itsourcecode Student Management System · SQL Injection

Affects itsourcecode Student 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.3% chance of exploitation in 30 days – higher than 32% 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 12 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
itsourcecode Student Management System	Affected =1.0	Fixed in–

AI-suggested

1. Immediate mitigation should focus on implementing strict input validation and sanitization for the ID parameter in /update_account.php to prevent SQL injection. 2. Employ parameterized queries or prepared statements in the application code to eliminate direct concatenation of user inputs into SQL commands. 3. If patching the software is not immediately possible due to lack of vendor updates, deploy Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the vulnerable endpoint. 4. Conduct thorough code reviews and security testing of the Student Management System to identify and remediate similar injection flaws. 5. Monitor database logs and application logs for unusual query patterns or errors indicative of injection attempts. 6. Restrict database user permissions to the minimum necessary to limit the impact of a successful injection. 7. Educate IT staff and administrators about this vulnerability and the importance of timely updates and monitoring. 8. Consider network segmentation to isolate the Student Management System from critical infrastructure to reduce potential lateral movement. 9. Maintain regular backups of the database to enable recovery in case of data corruption or loss. 10. Engage with the vendor or community to obtain patches or updates addressing this vulnerability as soon as they become available.

Description

A weakness has been identified in itsourcecode Student Management System 1.0. The affected element is an unknown function of the file /update_account.php. This manipulation of the argument ID causes sql injection. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be exploited.

Impact

For European organizations, especially educational institutions using the itsourcecode Student Management System 1.0, this vulnerability poses a significant risk to the confidentiality, integrity, and availability of student and administrative data. Successful exploitation could lead to unauthorized disclosure of personal information, manipulation of student records, or denial of service through database corruption. This could result in regulatory non-compliance with GDPR due to data breaches, reputational damage, and operational disruptions. The medium severity rating reflects that while the vulnerability is exploitable remotely without authentication, the impact is somewhat limited to the affected system and does not extend to broader network compromise. However, given the sensitive nature of educational data and the potential for cascading effects on institutional operations, the threat is non-trivial. European entities may face legal and financial consequences if breaches occur. The public availability of exploit code increases the likelihood of opportunistic attacks, making timely mitigation critical. Additionally, attackers could leverage this vulnerability as a foothold for further lateral movement within institutional networks if other security controls are weak.

Summary

CVE-2025-14578 identifies a SQL Injection vulnerability in the itsourcecode Student Management System version 1.0, located in the /update_account.php script. The vulnerability is triggered by manipulation of the ID parameter, which is not properly sanitized before being used in SQL queries. This allows an attacker to inject arbitrary SQL commands remotely without requiring authentication or user interaction. The CVSS 4.0 base score is 6.9 (medium), reflecting the ease of exploitation (network accessible, no privileges needed) and the partial impact on confidentiality, integrity, and availability. The vulnerability could enable attackers to extract sensitive data, modify records, or disrupt database operations. Although no active exploits have been reported in the wild, the public availability of exploit code increases the risk of exploitation. The affected product is primarily used in educational environments, where student data confidentiality and system integrity are critical. The lack of available patches necessitates immediate mitigation efforts. The vulnerability does not require user interaction, making automated exploitation feasible. The scope is limited to the Student Management System version 1.0, but given the critical nature of educational data, the impact can be significant. This vulnerability exemplifies common risks associated with improper input validation and highlights the need for secure coding practices in web applications handling sensitive data.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Dec 2025, 21:39 UTC

Technical details

References

Community reviews

Related threats