CVE-2025-14214VulnerabilityPublished 8 Dec 2025

CVE-2025-14214: itsourcecode Student Information System · SQL Injection

Affects itsourcecode Student Information SystemSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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: Low
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
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-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 Information System	Affected =1.0	Fixed in–

AI-suggested

Organizations should immediately audit their deployment of the itsourcecode Student Information System to identify affected versions. Since no official patches are currently available, administrators should implement the following mitigations: 1) Apply input validation and sanitization on the 'ID' parameter in /section_edit1.php to reject or properly escape malicious input. 2) Refactor database queries to use parameterized statements or prepared queries to prevent SQL injection. 3) Restrict network access to the application to trusted IP ranges where feasible, reducing exposure. 4) Monitor web application logs for suspicious query patterns or repeated access attempts targeting the vulnerable parameter. 5) Employ Web Application Firewalls (WAFs) with SQL injection detection and prevention rules tailored to block exploitation attempts. 6) Educate developers and administrators on secure coding and patch management practices. 7) Plan for an upgrade or patch deployment once the vendor releases a fix. 8) Conduct penetration testing and vulnerability scanning to verify the effectiveness of mitigations.

Description

CVE-2025-14214 is a medium severity SQL injection vulnerability found in itsourcecode Student Information System version 1.0, specifically in the /section_edit1.php file via the ID parameter. The flaw allows remote attackers to manipulate SQL queries without authentication or user interaction, potentially leading to unauthorized data access or modification. Although no public exploits are currently known in the wild, the vulnerability has been publicly disclosed, increasing the risk of exploitation. The vulnerability impacts confidentiality, integrity, and availability of the affected system's data. European educational institutions using this software could face data breaches or service disruptions if exploited. Mitigation requires immediate code review and patching to sanitize inputs, employing parameterized queries, and monitoring for suspicious activity. Countries with significant deployments of this software in education sectors or with strategic interest in protecting student data are at higher risk. Given the medium CVSS score and ease of remote exploitation without authentication, timely remediation is critical to prevent potential data compromise.

Impact

For European organizations, particularly educational institutions using the itsourcecode Student Information System 1.0, this vulnerability poses significant risks. Exploitation could lead to unauthorized disclosure of personal student data, violating GDPR and other privacy regulations, resulting in legal and financial penalties. Data integrity could be compromised, allowing attackers to alter student records, grades, or enrollment information, which could disrupt academic operations and damage institutional reputation. Availability impacts could arise if attackers execute destructive SQL commands, potentially causing denial of service or data loss. The remote and unauthenticated nature of the exploit increases the attack surface, making it easier for threat actors to target vulnerable systems from anywhere. Given the sensitivity of educational data and the increasing focus on protecting such information in Europe, this vulnerability could have serious operational and compliance consequences if not addressed promptly.

Summary

CVE-2025-14214 identifies a SQL injection vulnerability in itsourcecode Student Information System version 1.0, located in the /section_edit1.php script. The vulnerability arises from improper sanitization of the 'ID' parameter, which is directly used in SQL queries, allowing an attacker to inject malicious SQL code. This injection can be performed remotely without requiring authentication or user interaction, making it accessible to a wide range of attackers. The vulnerability impacts confidentiality by potentially exposing sensitive student information, integrity by allowing unauthorized modification of records, and availability if destructive queries are executed. The CVSS 4.0 score of 5.3 (medium) reflects the ease of exploitation (low attack complexity), no privileges required, and no user interaction needed, but limited impact on system confidentiality, integrity, and availability (low to limited). Although no known exploits are currently active in the wild, the public disclosure increases the risk of exploitation by opportunistic attackers. The affected product is primarily used in educational environments to manage student data, making the data highly sensitive and subject to privacy regulations such as GDPR. The lack of available patches or vendor advisories necessitates immediate mitigation efforts by users. The vulnerability's presence in a critical web application component underscores the importance of secure coding practices, including input validation and use of parameterized queries to prevent SQL injection attacks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Dec 2025, 05:02 UTC

Technical details

References

Community reviews

Related threats