CVE-2026-1545VulnerabilityPublished 28 Jan 2026Updated 23 Feb 2026

CVE-2026-1545: 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 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 28 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

To mitigate CVE-2026-1545, organizations should immediately implement input validation and sanitization for the 'ID' parameter in the /course/index.php file. Specifically, developers should refactor the code to use parameterized queries or prepared statements to prevent SQL injection. If source code access is limited, deploying a Web Application Firewall (WAF) with custom rules to detect and block SQL injection attempts targeting the vulnerable parameter can provide interim protection. Regularly monitoring logs for suspicious query patterns related to the 'ID' parameter is recommended. Organizations should also track vendor communications for official patches or updates and apply them promptly once available. Conducting security code reviews and penetration testing focused on injection flaws in the application will help identify and remediate similar vulnerabilities. Finally, educating developers on secure coding practices and enforcing least privilege principles on database accounts can reduce the attack surface.

Description

A weakness has been identified in itsourcecode School Management System 1.0. The affected element is an unknown function of the file /course/index.php. Executing a manipulation of the argument ID can lead to sql injection. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks.

Impact

The SQL injection vulnerability in itsourcecode School Management System 1.0 can have significant impacts on organizations, particularly educational institutions that rely on this software for managing sensitive student and course data. Successful exploitation can lead to unauthorized disclosure of confidential information, including personal identifiable information (PII) of students and staff. Attackers could also modify or delete critical data, disrupting school operations and undermining data integrity. In severe cases, attackers might escalate the attack to compromise the underlying database server or pivot to other internal systems, affecting availability and broader network security. The remote and unauthenticated nature of the exploit increases the risk of widespread automated attacks. Organizations failing to address this vulnerability may face reputational damage, regulatory penalties related to data protection laws, and operational downtime.

Summary

CVE-2026-1545 identifies a SQL injection vulnerability in itsourcecode School Management System version 1.0, located in the /course/index.php file. The vulnerability stems from insufficient input validation of the 'ID' parameter, which is directly used in SQL queries without proper sanitization or parameterization. This flaw allows remote attackers to inject malicious SQL code by manipulating the 'ID' argument, potentially leading to unauthorized data retrieval, modification, or deletion within the backend database. The attack vector requires no authentication or user interaction, increasing the risk of automated exploitation. The CVSS 4.0 base score is 6.9 (medium severity), reflecting the network attack vector, low complexity, and no privileges required. Although no known exploits are currently active in the wild, proof-of-concept exploits have been publicly disclosed, increasing the likelihood of future attacks. The vulnerability impacts confidentiality, integrity, and availability of the system's data, including sensitive educational records. No official patches or updates have been linked yet, so mitigation relies on implementing secure coding practices such as prepared statements and input validation. Organizations using this software should monitor for updates and apply fixes promptly to prevent exploitation.

References

Community reviews

Loading reviews…