VulnerabilityPublished 25 Feb 2026

CVE-2026-3150: itsourcecode College Management System · SQL Injection

Affects itsourcecode College Management SystemSource CVE Database V5

Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 30 Oct 2026, 06:59 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 23% 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 25 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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
itsourcecodeCollege Management System	Affected =1.0	Fixed in–

AI-suggested

Immediately audit all instances of itsourcecode College Management System version 1.0 to identify vulnerable deployments.
Implement strict input validation and sanitization for the teacher_id parameter, ensuring only expected data types and formats are accepted.
Refactor the affected code to use parameterized queries or prepared statements to prevent SQL injection.
Restrict database user privileges to the minimum necessary, limiting the potential damage from successful exploitation.
Deploy web application firewalls (WAFs) with rules targeting SQL injection patterns to provide an additional layer of defense.
Monitor logs for suspicious database queries or repeated access attempts to /admin/display-teacher.php.
Isolate the College Management System from public networks where possible, restricting access to trusted IP ranges.
Engage with the vendor or community to obtain or develop official patches and apply them promptly once available.
Educate administrators and developers on secure coding practices to prevent similar vulnerabilities in future releases.
Consider network segmentation and regular backups to facilitate recovery in case of data compromise.

Description

A security vulnerability has been detected in itsourcecode College Management System 1.0. This affects an unknown part of the file /admin/display-teacher.php. The manipulation of the argument teacher_id leads to sql injection. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used.

Impact

The exploitation of CVE-2026-3150 can lead to unauthorized disclosure of sensitive educational data, including personal information of students and faculty, grades, and administrative records. Attackers could manipulate or delete data, undermining data integrity and potentially disrupting academic operations. The vulnerability's remote exploitability without authentication increases the attack surface, allowing external threat actors to target vulnerable systems directly. This could result in reputational damage, regulatory penalties related to data protection laws, and operational downtime. Educational institutions relying on the affected software may face significant challenges in maintaining trust and compliance. Furthermore, attackers could leverage the vulnerability as a foothold for further network compromise. The medium severity score reflects a balanced risk, but the real-world impact depends on the sensitivity of the data stored and the presence of additional security controls. Since no patches are currently available, the window of exposure remains open, increasing the urgency for mitigation.

Summary

CVE-2026-3150 identifies a SQL injection vulnerability in itsourcecode College Management System version 1.0, located in the /admin/display-teacher.php script. The vulnerability stems from insufficient input validation of the teacher_id parameter, which is directly used in SQL queries without proper sanitization or parameterization. This flaw allows remote attackers to inject arbitrary SQL code, potentially enabling unauthorized access to sensitive data, modification of database contents, or disruption of service. The attack vector requires no user interaction and no authentication, making it remotely exploitable over the network. The CVSS 4.0 base score is 5.3 (medium), reflecting the moderate impact on confidentiality, integrity, and availability, and the relatively low complexity of exploitation. Although no known exploits are currently active in the wild, the public disclosure of the vulnerability increases the likelihood of exploitation attempts. The lack of available patches necessitates immediate mitigation efforts by affected organizations. This vulnerability is particularly critical in educational environments where the College Management System is deployed, as it may expose sensitive student and faculty information. The vulnerability does not require special privileges or user interaction, increasing its risk profile. The absence of secure coding practices such as prepared statements or stored procedures in the affected code is the root cause. Organizations should audit their systems for this version and implement compensating controls until an official patch is released.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Feb 2026, 05:11 UTC

Technical details

References

Community reviews

Related threats