CVE-2025-14336VulnerabilityPublished 9 Dec 2025

CVE-2025-14336: 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 9 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

Since no official patches are currently available, organizations should immediately implement input validation and sanitization on the 'sy' parameter in /promote.php to block malicious SQL payloads. Employ parameterized queries or prepared statements to prevent injection attacks. Restrict network access to the Student Management System to trusted IP ranges and deploy web application firewalls (WAFs) with SQL injection detection rules to detect and block exploit attempts. Conduct thorough code reviews and security testing of the application to identify and remediate similar vulnerabilities. Monitor logs for suspicious database queries or unusual application behavior. Educate administrators on the risk and ensure backups of critical data are maintained to enable recovery in case of compromise. Engage with the vendor or community to obtain or develop official patches. Consider isolating the affected system within a segmented network zone to limit potential lateral movement.

Description

A vulnerability was found in itsourcecode Student Management System 1.0. Affected by this issue is some unknown functionality of the file /promote.php. The manipulation of the argument sy results in sql injection. It is possible to launch the attack remotely. The exploit has been made public and could be used.

Impact

For European organizations, particularly educational institutions using the itsourcecode Student Management System 1.0, this vulnerability could lead to unauthorized disclosure of sensitive student and staff information, including personal identification and academic records. The integrity of student promotion data could be compromised, leading to inaccurate academic results or administrative errors. Availability of the system may also be affected if attackers execute destructive SQL commands or cause database corruption. Such incidents could result in regulatory non-compliance with GDPR due to data breaches, reputational damage, and potential financial penalties. The remote and unauthenticated nature of the exploit increases the attack surface, making even less technically sophisticated attackers capable of exploiting the flaw. The public availability of exploit code further elevates the risk of opportunistic attacks targeting vulnerable installations. Disruption of educational services could impact teaching and administrative operations, especially during critical academic periods.

Summary

CVE-2025-14336 identifies a SQL injection vulnerability in the itsourcecode Student Management System version 1.0, affecting the /promote.php endpoint through the 'sy' parameter. This vulnerability allows an attacker to remotely inject crafted SQL statements without requiring authentication or user interaction, exploiting insufficient input validation or improper sanitization of the 'sy' parameter. The injection can lead to unauthorized access to the database, enabling attackers to read, modify, or delete sensitive student records or administrative data. The CVSS 4.0 score of 6.9 (medium severity) reflects the network attack vector, low complexity, no privileges or user interaction needed, but limited impact on confidentiality, integrity, and availability. Although no active exploits have been reported in the wild, the public disclosure of the exploit code increases the risk of exploitation. The vulnerability stems from poor coding practices in handling user-supplied input in a critical student management function, potentially allowing attackers to escalate their impact by manipulating student promotion data. The lack of vendor patches or official remediation guidance necessitates immediate defensive measures by administrators. Given the critical nature of educational data and the widespread use of student management systems, this vulnerability poses a tangible threat to data security and operational continuity.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Dec 2025, 19:30 UTC

Technical details

References

Community reviews

Related threats