CVE-2025-14257VulnerabilityPublished 8 Dec 2025

CVE-2025-14257: 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 26 Oct 2026, 08:30 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 41% 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 8 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 26 Oct 2026.

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 application of vendor patches or updates once available. 2. If patches are unavailable, implement input validation and sanitization on the 'ID' parameter to reject malicious input. 3. Refactor the vulnerable code to use parameterized queries or prepared statements to prevent SQL injection. 4. Deploy Web Application Firewalls (WAFs) with rules to detect and block SQL injection attempts targeting /newrecord.php. 5. Conduct thorough vulnerability scanning across all educational systems to identify instances of the affected software. 6. Enhance logging and monitoring to detect unusual database queries or access patterns. 7. Restrict database user privileges to the minimum necessary to limit the impact of potential exploitation. 8. Educate IT staff in educational institutions about this vulnerability and recommended response actions. 9. Consider network segmentation to isolate critical student management systems from broader networks. 10. Regularly back up databases and verify backup integrity to enable recovery in case of data tampering or loss.

Description

A flaw has been found in itsourcecode Student Management System 1.0. Affected is an unknown function of the file /newrecord.php. Executing manipulation of the argument ID can lead to sql injection. The attack can be launched remotely. The exploit has been published and may be used.

Impact

For European organizations, especially educational institutions using the itsourcecode Student Management System 1.0, this vulnerability could lead to significant data breaches involving personal student information, violating GDPR and other data protection laws. Unauthorized access or manipulation of student records can damage institutional reputation, result in legal penalties, and disrupt academic operations. The remote and unauthenticated nature of the exploit increases the attack surface, potentially allowing widespread exploitation if the software is deployed in multiple institutions. The integrity of academic records could be compromised, affecting student evaluations and certifications. Additionally, availability impacts could arise if attackers execute destructive SQL commands, causing denial of service. The exposure of sensitive data may also facilitate further targeted attacks against institutions. Given the critical role of educational data, the threat is particularly concerning for European countries with large deployments of this system or similar legacy platforms.

Summary

CVE-2025-14257 identifies a SQL injection vulnerability in the itsourcecode Student Management System version 1.0, located in the /newrecord.php script. The vulnerability arises from improper sanitization of the 'ID' parameter, allowing an attacker to inject malicious SQL code remotely without authentication or user interaction. The CVSS 4.0 score of 6.9 reflects a medium severity, considering the attack vector is network-based with low complexity and no privileges or user interaction required. The vulnerability can lead to unauthorized data access, modification, or deletion within the backend database, impacting confidentiality, integrity, and availability. Although no exploits are currently known in the wild, the public availability of exploit code increases the likelihood of attacks. The Student Management System is typically used by educational institutions to manage student records, making the data highly sensitive. The lack of patches or vendor-provided fixes necessitates immediate mitigation through secure coding practices such as parameterized queries, input validation, and web application firewalls. Monitoring and logging should be enhanced to detect potential exploitation attempts. This vulnerability exemplifies the risks associated with legacy or poorly maintained educational software systems.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Dec 2025, 17:43 UTC

Technical details

References

Community reviews

Related threats