VulnerabilityPublished 25 Feb 2026

CVE-2026-3149: 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 24% 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

Organizations should immediately audit their use of the itsourcecode College Management System version 1.0 and restrict access to the /admin/asign-single-student-subjects.php endpoint. Since no official patches are currently available, administrators must implement strict input validation on the 'course_code' parameter, ensuring only expected values are accepted. Employing parameterized queries or prepared statements in the backend code is essential to prevent SQL injection. Web application firewalls (WAFs) can be configured to detect and block suspicious SQL injection attempts targeting this parameter. Regular database backups and monitoring for unusual query patterns can help mitigate damage if exploitation occurs. Additionally, organizations should plan to upgrade to patched versions once released and conduct security training for developers to avoid similar vulnerabilities. Restricting administrative interface access to trusted IPs and enforcing strong authentication can further reduce risk.

Description

A weakness has been identified in itsourcecode College Management System 1.0. Affected by this issue is some unknown functionality of the file /admin/asign-single-student-subjects.php. Executing a manipulation of the argument course_code can lead to sql injection. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks.

Impact

The exploitation of this SQL injection vulnerability can lead to unauthorized access to sensitive academic and student information stored in the database, including grades, enrollment details, and personal data. Attackers could modify or delete records, impacting data integrity and potentially disrupting academic operations. Confidentiality breaches could result in privacy violations and regulatory non-compliance, especially under data protection laws like GDPR or FERPA. Availability could be affected if attackers execute destructive queries or cause database errors, leading to denial of service for legitimate users. Although the vulnerability requires no authentication and is remotely exploitable, the limited scope of the affected functionality and the medium CVSS score suggest the impact is significant but not critical. Organizations worldwide using this CMS without proper mitigation are at risk of data compromise and operational disruption.

Summary

CVE-2026-3149 identifies a SQL injection vulnerability in the itsourcecode College Management System version 1.0, specifically within the /admin/asign-single-student-subjects.php script. The vulnerability arises from insufficient input validation of the 'course_code' parameter, which is directly incorporated into SQL queries without proper sanitization or use of parameterized statements. This flaw allows remote attackers to manipulate SQL commands by injecting crafted input, potentially enabling unauthorized data access, modification, or deletion within the backend database. The attack vector is network accessible without requiring user authentication or interaction, making it relatively easy to exploit. However, the impact is somewhat limited as the vulnerability affects only a specific function and the overall scope of data exposure or control is partial. The CVSS 4.0 score of 5.3 reflects these factors, indicating a medium severity level. No patches have been officially released yet, and no active exploitation has been reported, but public exploit code availability increases the risk. The vulnerability primarily threatens educational institutions using this CMS version, potentially exposing sensitive student and academic data.

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