CVE-2026-1176VulnerabilityPublished 19 Jan 2026Updated 23 Feb 2026

CVE-2026-1176: 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 26 Oct 2026, 06:26 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 19 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-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
itsourcecodeSchool Management System	Affected =1.0	Fixed in–

CPE configurations (1)

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

AI-suggested

1. Immediately implement input validation and parameterized queries or prepared statements in the /subject/index.php file to sanitize the 'ID' parameter and prevent SQL injection. 2. Deploy a Web Application Firewall (WAF) with rules specifically designed to detect and block SQL injection attempts targeting the vulnerable parameter. 3. Conduct a thorough code review of the entire application to identify and remediate similar injection flaws. 4. Monitor database logs and web server access logs for unusual or suspicious queries indicative of exploitation attempts. 5. Restrict database user permissions to the minimum necessary to limit the impact of any successful injection. 6. If patching is not immediately possible, consider isolating the affected system from external networks or limiting access to trusted IP addresses. 7. Educate developers and administrators about secure coding practices and the risks of SQL injection. 8. Prepare an incident response plan to quickly address any detected exploitation. 9. Stay updated with vendor advisories for official patches or updates. 10. Consider migrating to alternative, actively maintained school management systems if remediation is not feasible.

Description

A security flaw has been discovered in itsourcecode School Management System 1.0. Affected is an unknown function of the file /subject/index.php. Performing a manipulation of the argument ID results in sql injection. It is possible to initiate the attack remotely. The exploit has been released to the public and may be used for attacks.

Impact

The SQL injection vulnerability can lead to unauthorized disclosure of sensitive student and school data, including personal information, grades, and administrative records. Attackers could manipulate or delete data, compromising data integrity and potentially disrupting school operations. The ability to execute arbitrary SQL commands remotely without authentication increases the risk of data breaches and system downtime. Organizations using this system may face regulatory compliance issues, reputational damage, and operational interruptions. While the impact is medium severity, the exposure of educational data can have serious privacy implications, especially for minors. The exploitability without user interaction or privileges broadens the threat landscape, enabling automated attacks or mass exploitation campaigns. The absence of patches means organizations must rely on interim mitigations, increasing operational complexity. If attackers chain this vulnerability with others, the overall impact could escalate. The threat is particularly relevant for educational institutions with limited cybersecurity resources.

Summary

CVE-2026-1176 identifies a SQL injection vulnerability in the itsourcecode School Management System version 1.0, located in the /subject/index.php file. The vulnerability arises from improper sanitization of the 'ID' parameter, which can be manipulated remotely without any authentication or user interaction. This allows attackers to inject malicious SQL code, potentially extracting, modifying, or deleting data within the backend database. The vulnerability is exploitable over the network, increasing the attack surface. The CVSS 4.0 vector indicates no privileges or user interaction are required, and the attack complexity is low. The impact on confidentiality, integrity, and availability is limited but present, as attackers can access or alter sensitive educational data. Although no patches or fixes have been linked yet, the public availability of exploit code raises the urgency for mitigation. The vulnerability does not affect the system's security controls or require special conditions, making it accessible to a broad range of attackers. The lack of known exploits in the wild suggests either limited deployment or recent disclosure. However, the risk remains significant for organizations relying on this software for managing student and academic information.

References

Community reviews

Loading reviews…