CVE-2025-13325VulnerabilityPublished 18 Nov 2025

CVE-2025-13325: 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 26 Oct 2026, 06:26 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 18 Nov 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 Information System	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2025-13325, organizations should immediately implement input validation and sanitization on the en_id parameter to prevent injection of malicious SQL code. Employing parameterized queries or prepared statements is essential to ensure that user input is treated as data rather than executable code. Restrict database user permissions to the minimum necessary to limit the impact of any successful injection. If patches or updates from itsourcecode become available, they should be applied promptly. In the absence of official patches, consider deploying web application firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the vulnerable parameter. Conduct thorough code reviews and security testing of the SIS application to identify and remediate similar injection points. Regularly monitor logs for suspicious database query patterns or anomalies. Additionally, ensure that backups of student data are maintained securely to enable recovery in case of data corruption or loss. Educate IT staff and administrators about the vulnerability and the importance of timely remediation.

Description

A vulnerability was determined in itsourcecode Student Information System 1.0. The affected element is an unknown function of the file /enrollment_edit1.php. Executing manipulation of the argument en_id can lead to sql injection. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized.

Impact

For European organizations, especially educational institutions using the itsourcecode Student Information System 1.0, this vulnerability poses a significant risk to the confidentiality, integrity, and availability of student data. Exploitation could lead to unauthorized access to sensitive personal information, including enrollment records, grades, and possibly financial data. This could result in data breaches subject to GDPR penalties, reputational damage, and loss of trust. Integrity of data could be compromised, leading to incorrect academic records or enrollment statuses, disrupting administrative processes. Availability could also be affected if attackers execute destructive queries or cause database corruption. The remote and unauthenticated nature of the vulnerability increases the attack surface, making it easier for threat actors to target multiple institutions. Given the critical role of student information systems in educational operations, exploitation could disrupt academic activities and compliance reporting. The medium severity score suggests moderate but non-negligible risk, warranting prompt remediation to avoid escalation or chaining with other vulnerabilities.

Summary

CVE-2025-13325 is a SQL injection vulnerability identified in the itsourcecode Student Information System (SIS) version 1.0. The vulnerability resides in the /enrollment_edit1.php script, where the en_id parameter is improperly sanitized, allowing an attacker to inject malicious SQL code. This injection flaw can be exploited remotely without authentication or user interaction, enabling attackers to manipulate backend database queries. Potential consequences include unauthorized retrieval, modification, or deletion of sensitive student information stored in the database. The vulnerability has a CVSS 4.0 base score of 5.3, reflecting medium severity due to low complexity of attack and no required privileges, but limited impact scope and partial confidentiality, integrity, and availability impact. Although no public patches have been released, the exploit details have been disclosed, increasing the risk of exploitation. The vulnerability affects only version 1.0 of the software, and no known exploits are currently active in the wild. The lack of authentication requirement and remote attack vector make this vulnerability particularly concerning for institutions relying on this SIS for managing enrollment and student data. The vulnerability highlights the importance of secure coding practices such as 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 25 Nov 2025, 01:07 UTC

Technical details

References

Community reviews

Related threats