CVE-2025-14256VulnerabilityPublished 8 Dec 2025

CVE-2025-14256: 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, 06:26 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 2026-10-26.

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

Organizations should immediately audit their use of the itsourcecode Student Management System to identify deployments of version 1.0. Since no official patches are currently available, implement the following mitigations: 1) Apply strict input validation and sanitization on the 'ID' parameter in /newcurriculm.php, ideally replacing dynamic SQL queries with parameterized prepared statements to prevent injection. 2) Employ web application firewalls (WAFs) with rules designed to detect and block SQL injection attempts targeting this endpoint. 3) Restrict network access to the Student Management System to trusted IP ranges and enforce strong authentication mechanisms where possible. 4) Monitor logs for suspicious query patterns or repeated access attempts to /newcurriculm.php. 5) Consider isolating the affected system within segmented network zones to limit potential lateral movement. 6) Engage with the vendor or community to obtain or develop patches and apply them as soon as they become available. 7) Educate IT staff on the risks and detection methods for SQL injection attacks specific to this product. These targeted actions go beyond generic advice and address the vulnerability's specific exploitation vector.

Description

A vulnerability was detected in itsourcecode Student Management System 1.0. This impacts an unknown function of the file /newcurriculm.php. Performing manipulation of the argument ID results in sql injection. The attack can be initiated remotely. The exploit is now public and may be used.

Impact

For European organizations, particularly educational institutions using the itsourcecode Student Management System 1.0, this vulnerability poses a significant risk of unauthorized data exposure and manipulation. Compromise could lead to leakage of sensitive student and staff information, alteration of academic records, and disruption of educational services. Such incidents could result in regulatory non-compliance under GDPR, leading to legal and financial penalties. The ability to exploit the vulnerability remotely without authentication increases the attack surface, potentially allowing attackers to target multiple institutions simultaneously. Given the critical role of student management systems in academic operations, exploitation could disrupt administrative workflows and damage institutional reputation. Additionally, attackers could leverage this vulnerability as a foothold for further network intrusion or lateral movement. The medium severity rating suggests moderate but tangible risks, emphasizing the need for timely mitigation to prevent escalation. The public availability of exploit code increases the urgency for European organizations to assess and remediate affected systems promptly.

Summary

CVE-2025-14256 identifies a SQL injection vulnerability in the itsourcecode Student Management System version 1.0, specifically within the /newcurriculm.php script. The vulnerability arises from improper sanitization of the 'ID' parameter, allowing attackers to inject malicious SQL statements. This flaw can be exploited remotely without any authentication or user interaction, enabling attackers to manipulate backend database queries. The CVSS 4.0 score of 6.9 reflects a medium severity, indicating a significant risk but not critical. Exploitation could lead to unauthorized data access, modification, or deletion, potentially impacting student records and administrative data. The vulnerability does not require privileges or user interaction, increasing its risk profile. Although no official patches or fixes have been released, the exploit code is publicly available, raising the likelihood of exploitation attempts. The lack of known exploits in the wild suggests it is a newly disclosed vulnerability, but the presence of public exploit code necessitates urgent attention. The vulnerability affects only version 1.0 of the product, which may limit its scope depending on deployment prevalence. The absence of CWE classification limits detailed technical categorization, but the nature of the flaw aligns with common SQL injection issues. Overall, this vulnerability represents a critical risk to the confidentiality, integrity, and availability of educational data managed by the affected system.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats