CVE-2026-1701VulnerabilityPublished 30 Jan 2026Updated 23 Feb 2026

CVE-2026-1701: itsourcecode School Management System · SQL Injection

Affects itsourcecode School 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 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 30 Jan 2026
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
itsourcecodeSchool Management System	Affected =1.0	Fixed in–

CPE configurations (1)

cpe:2.3:a:itsourcecode:school_management_system:*:*:*:*:*:*:*:*

AI-suggested

Given the lack of official patches for CVE-2026-1701, organizations should implement multiple layers of defense to mitigate risk. First, apply strict input validation and sanitization on the ID parameter in /enrollment/index.php to prevent SQL injection, using parameterized queries or prepared statements if possible. Deploy a web application firewall (WAF) configured to detect and block SQL injection attempts targeting this endpoint. Restrict network access to the vulnerable application by limiting exposure to trusted IP ranges and segmenting the network to isolate critical systems. Conduct regular security assessments and code reviews to identify and remediate similar injection flaws. Monitor application logs for suspicious query patterns indicative of injection attempts. If feasible, upgrade to a newer, patched version of the software once available or consider alternative school management solutions with better security track records. Educate IT staff and administrators about the vulnerability and ensure incident response plans are updated to handle potential exploitation scenarios.

Description

A security vulnerability has been detected in itsourcecode School Management System 1.0. This issue affects some unknown processing of the file /enrollment/index.php. Such manipulation of the argument ID leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used. Due to contradicting product definitions in the original disclosure, this CVE was initially incorrectly assigned to the Student Management System.

Impact

The potential impact of CVE-2026-1701 is significant for organizations using the affected itsourcecode School Management System version 1.0. Successful exploitation could allow attackers to access, modify, or delete sensitive enrollment and student data, leading to breaches of confidentiality and integrity. Data manipulation could also disrupt school administrative functions, affecting availability and operational continuity. Since the vulnerability requires no authentication or user interaction, it can be exploited remotely by any attacker with network access to the vulnerable endpoint, increasing the attack surface. Educational institutions often hold personally identifiable information (PII) and academic records, making them attractive targets for data theft or ransomware attacks. The absence of known exploits in the wild currently limits immediate widespread impact, but public disclosure raises the likelihood of future attacks. Organizations failing to address this vulnerability risk reputational damage, regulatory penalties related to data protection laws, and operational disruptions.

Summary

CVE-2026-1701 is a SQL Injection vulnerability identified in the itsourcecode School Management System version 1.0. The vulnerability resides in the /enrollment/index.php script, where the ID parameter is improperly sanitized, allowing attackers to inject malicious SQL queries. This flaw enables remote exploitation without requiring authentication or user interaction, making it accessible to any attacker who can reach the vulnerable endpoint. The injection can lead to unauthorized data retrieval, modification, or deletion within the backend database, impacting confidentiality, integrity, and availability. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P) reflects that the attack is network-based with low complexity and no privileges or user interaction needed, but with limited impact on confidentiality, integrity, and availability. The vulnerability was initially misattributed to a different product due to conflicting product definitions but has since been correctly assigned to the itsourcecode School Management System. No official patches or fixes have been published yet, and no known exploits are reported in the wild, though public disclosure increases the risk of future exploitation. This vulnerability is particularly concerning for educational institutions relying on this software version, as exploitation could expose sensitive student and enrollment data or disrupt school operations.

References

Community reviews

Loading reviews…