CVE-2025-15198VulnerabilityPublished 29 Dec 2025Updated 24 Feb 2026

CVE-2025-15198: code-projects College Notes Uploading System · SQL Injection

Affects code-projects College Notes Uploading SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 18:53 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 29 Dec 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 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
GitHublimingqian123/CVE`pkg:github/limingqian123/CVE`Other threats	Affected =1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-15198, organizations should immediately implement input validation and sanitization on the 'User' parameter within /login.php to prevent SQL injection. Employing parameterized queries or prepared statements is critical to ensure that user input is not directly concatenated into SQL commands. Until an official patch is released by the vendor, administrators should consider deploying web application firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting this endpoint. Conduct thorough code reviews and security testing on all user input handling components of the application. Restrict database user permissions to the minimum necessary to limit potential damage from exploitation. Monitor logs for suspicious activities related to login attempts and SQL errors. Additionally, organizations should plan to upgrade to a patched version once available and educate developers on secure coding practices to prevent similar vulnerabilities in the future.

Description

A weakness has been identified in code-projects College Notes Uploading System 1.0. This issue affects some unknown processing of the file /login.php. Executing a manipulation of the argument User can lead to sql injection. The attack may be launched remotely. The exploit has been made available to the public and could be used for attacks.

Impact

The potential impact of CVE-2025-15198 is significant for organizations using the affected College Notes Uploading System 1.0. Successful exploitation can lead to unauthorized disclosure of sensitive data, including user credentials and uploaded academic content, undermining confidentiality. Attackers may also alter or delete data, affecting data integrity and potentially disrupting the availability of the service. This can result in reputational damage, loss of trust from students and faculty, and possible regulatory compliance violations related to data protection. Educational institutions relying on this system for note sharing and collaboration may face operational disruptions and increased risk of further attacks leveraging stolen credentials or data. The remote, unauthenticated nature of the vulnerability increases the attack surface, allowing widespread scanning and exploitation attempts. While no active exploitation is currently known, the public exploit availability means attackers can readily weaponize this vulnerability, posing a persistent threat until remediated.

Summary

CVE-2025-15198 identifies an SQL injection vulnerability in the College Notes Uploading System version 1.0 developed by code-projects. The flaw exists in the /login.php endpoint, where the 'User' parameter is improperly sanitized or validated, allowing attackers to inject malicious SQL payloads. This vulnerability can be exploited remotely without any authentication or user interaction, making it highly accessible to attackers. The injection can lead to unauthorized access to the backend database, enabling attackers to read, modify, or delete sensitive data, potentially compromising user credentials and other stored information. The CVSS v4.0 score of 6.9 reflects a medium severity, considering the ease of exploitation (network vector, no privileges or user interaction required) but limited scope of impact (partial confidentiality, integrity, and availability). Although no confirmed active exploitation has been reported, the public availability of an exploit code increases the risk of future attacks. The lack of official patches or updates at the time of publication necessitates immediate mitigation efforts by administrators. This vulnerability highlights the critical need for secure coding practices, especially in web applications handling user authentication and data uploads in educational environments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:37 UTC

Technical details

References

Community reviews

Related threats