VulnerabilityPublished 8 Oct 2025Updated 24 Feb 2026

CVE-2025-11434: itsourcecode Student Transcript Processing System · SQL Injection

Affects itsourcecode Student Transcript Processing SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 08:30 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 8 Oct 2025
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 26 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.
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
itsourcecode Student Transcript Processing System	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2025-11434, organizations should immediately implement strict input validation and sanitization on the 'uname' parameter within /login.php to prevent malicious SQL code injection. Employing parameterized queries or prepared statements is critical to eliminate direct concatenation of user input into SQL commands. Until an official patch is released by itsourcecode, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the vulnerable parameter. Conduct thorough code reviews and penetration testing focused on SQL injection vectors in the application. Restrict database user privileges to the minimum necessary to limit the impact of any successful injection. Monitor logs for suspicious query patterns or repeated failed login attempts indicative of exploitation attempts. Plan for timely patch deployment once available and maintain an incident response plan to address potential breaches. Additionally, educate developers on secure coding practices to prevent similar vulnerabilities in future releases.

Description

A weakness has been identified in itsourcecode Student Transcript Processing System 1.0. Affected is an unknown function of the file /login.php. Executing a manipulation of the argument uname can lead to sql injection. It is possible to launch the attack remotely. The exploit has been made available to the public and could be used for attacks.

Impact

The primary impact of CVE-2025-11434 is unauthorized access to or manipulation of student transcript data stored within the affected system's database. Attackers exploiting this vulnerability can execute arbitrary SQL commands, potentially leading to data leakage of sensitive personal and academic information, data corruption, or deletion. This compromises the confidentiality and integrity of student records, which can have severe reputational and legal consequences for educational institutions. While availability impact is limited, attackers could disrupt login functionality or database operations. The remote, unauthenticated nature of the exploit increases the risk of widespread attacks, especially since exploit code is publicly available. Organizations worldwide using this software version face risks of data breaches, regulatory non-compliance, and loss of trust. The medium severity rating reflects a balance between ease of exploitation and the limited scope of affected systems, but the sensitive nature of the data involved elevates the overall risk profile.

Summary

CVE-2025-11434 identifies a SQL injection vulnerability in the itsourcecode Student Transcript Processing System version 1.0, specifically within the /login.php file's 'uname' parameter. The vulnerability arises from improper input sanitization, allowing an attacker to inject malicious SQL code remotely without requiring authentication or user interaction. This can lead to unauthorized database queries, potentially exposing or altering sensitive student transcript data. The vulnerability has a CVSS 4.0 base score of 6.9, indicating medium severity, with attack vector being network-based and no privileges or user interaction needed. The impact on confidentiality, integrity, and availability is limited but non-negligible, as attackers could extract or manipulate data. Although no active exploitation has been reported, the public availability of exploit code increases the risk of future attacks. The vulnerability affects only version 1.0 of the product, and no official patches have been released yet. The lack of scope change means the vulnerability affects only the vulnerable component. Organizations using this system, especially educational institutions managing student records, are at risk. The vulnerability underscores the importance of secure coding practices such as parameterized queries and input validation to prevent SQL injection attacks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 21:58 UTC

Technical details

References

Community reviews

Related threats