CVE-2025-15075VulnerabilityPublished 25 Dec 2025Updated 26 Dec 2025

CVE-2025-15075: 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.4% chance of exploitation in 30 days – higher than 36% 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 25 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

Immediate mitigation steps include implementing strict input validation and sanitization on the 'ID' parameter within /student_p.php to prevent injection of malicious SQL code. Refactoring the code to use parameterized queries or prepared statements is essential to eliminate SQL injection risks. Organizations should conduct a thorough code review and security audit of the entire application to identify and remediate similar vulnerabilities. Network-level protections such as web application firewalls (WAFs) can be configured to detect and block SQL injection attempts targeting this endpoint. Monitoring database logs and application logs for unusual query patterns or errors can help detect exploitation attempts early. Since no official patches are available, organizations should consider isolating or restricting access to the vulnerable system until remediation is complete. Additionally, regular backups of critical data should be maintained to enable recovery in case of data corruption or loss. Educating IT staff and users about the vulnerability and encouraging prompt reporting of suspicious activity will enhance overall security posture.

Description

CVE-2025-15075 is a medium-severity SQL injection vulnerability affecting itsourcecode Student Management System version 1.0. The flaw exists in the /student_p.php file where manipulation of the ID parameter allows an unauthenticated attacker to execute arbitrary SQL commands remotely without user interaction. Although the CVSS score is 6.9, indicating a moderate risk, the vulnerability can lead to partial confidentiality, integrity, and availability impacts. No patches are currently available, and no known exploits have been observed in the wild yet. European educational institutions using this software are at risk of data breaches or system compromise. Mitigation requires immediate input validation, parameterized queries, and monitoring for suspicious database activity. Countries with significant adoption of this product or similar educational management systems, such as Germany, France, and the UK, are more likely to be affected.

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 data. Exploitation could lead to unauthorized disclosure of personal data, violating GDPR and other privacy laws, resulting in legal and financial penalties. Data integrity could be compromised by unauthorized modification of student records, affecting academic outcomes and institutional reputation. Availability impacts could disrupt administrative operations, causing delays and operational inefficiencies. The remote and unauthenticated nature of the exploit increases the likelihood of attacks, potentially from opportunistic or targeted threat actors. The public availability of the exploit code further elevates the risk of widespread exploitation. European organizations may face increased scrutiny from regulators and damage to trust from students, parents, and staff if breaches occur.

Summary

CVE-2025-15075 identifies a SQL injection vulnerability in itsourcecode Student Management System version 1.0, specifically within the /student_p.php endpoint. The vulnerability arises from insufficient sanitization or improper handling of the 'ID' parameter, allowing attackers to inject malicious SQL code. This injection can be performed remotely without requiring authentication or user interaction, increasing the attack surface significantly. The vulnerability allows attackers to manipulate backend database queries, potentially leading to unauthorized data access, data modification, or denial of service. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and partial impacts on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). Although no patches or official fixes have been released, the public disclosure of the exploit increases the risk of exploitation. The vulnerability is particularly concerning for educational institutions that rely on this software to manage sensitive student data, including personal information and academic records. Attackers exploiting this flaw could exfiltrate sensitive data, alter records, or disrupt system availability, impacting operational continuity and compliance with data protection regulations such as GDPR.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 1 Jan 2026, 22:37 UTC

Technical details

References

Community reviews

Related threats