CVE-2025-15053VulnerabilityPublished 24 Dec 2025

CVE-2025-15053: code-projects Student Information System · SQL Injection

Affects code-projects Student Information SystemSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 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 31% 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 24 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
code-projects Student Information System	Affected =1.0	Fixed in–

AI-suggested

1. Immediate code review and remediation to implement parameterized queries or prepared statements for all database interactions involving user inputs, especially the 'searchbox' parameter in /searchresults.php. 2. Apply rigorous input validation and sanitization to reject or neutralize malicious SQL syntax before processing. 3. Deploy Web Application Firewalls (WAFs) configured to detect and block SQL injection patterns targeting the affected endpoint. 4. Restrict database user permissions to the minimum necessary to limit the impact of potential exploitation. 5. Monitor application logs and network traffic for unusual query patterns or repeated failed attempts indicative of injection attacks. 6. If vendor patches become available, prioritize their deployment in test and production environments. 7. Conduct security awareness training for developers and administrators on secure coding practices and vulnerability management. 8. Implement network segmentation to isolate critical student information systems from broader enterprise networks. 9. Regularly back up databases and verify backup integrity to enable recovery in case of data corruption or loss. 10. Engage in threat intelligence sharing with other educational institutions and cybersecurity bodies to stay informed of emerging exploitation trends.

Description

A flaw has been found in code-projects Student Information System 1.0. This issue affects some unknown processing of the file /searchresults.php. Executing manipulation of the argument searchbox can lead to sql injection. The attack may be performed from remote. The exploit has been published and may be used.

Impact

For European organizations, particularly educational institutions using the code-projects Student Information System, this vulnerability poses a significant risk of unauthorized access to sensitive student data, including personal and academic records. Exploitation could result in data breaches, loss of data integrity through unauthorized modifications, or denial of service if the database is manipulated or corrupted. Such incidents could lead to regulatory non-compliance, especially under GDPR, resulting in legal penalties and reputational damage. The remote and unauthenticated nature of the exploit increases the attack surface, making it easier for threat actors to target vulnerable systems from anywhere. Disruption of student information systems can also impact educational operations and trust in digital infrastructure. Given the medium severity, the impact is serious but may be contained if mitigations are promptly applied. However, the presence of publicly available exploit code elevates the urgency for European organizations to address this vulnerability proactively.

Summary

CVE-2025-15053 identifies a SQL injection vulnerability in the code-projects Student Information System version 1.0, specifically in the /searchresults.php endpoint. The vulnerability arises from improper handling of the 'searchbox' parameter, which is susceptible to injection of malicious SQL code. An attacker can remotely exploit this flaw without any authentication or user interaction, leveraging the vulnerability to execute arbitrary SQL commands on the backend database. This can lead to unauthorized data access, modification, or deletion, impacting the confidentiality, integrity, and availability of student information stored within the system. The CVSS 4.0 score of 6.9 reflects a medium severity, considering the ease of exploitation (attack complexity low, no privileges or user interaction required) but limited scope of impact (partial confidentiality, integrity, and availability). Although no active exploits have been reported in the wild, the public availability of exploit code increases the likelihood of attacks. The vulnerability is particularly concerning for educational institutions relying on this system for managing sensitive student data. The lack of vendor patches or official remediation guidance necessitates immediate implementation of secure coding practices such as input validation and prepared statements to mitigate risk. Network-level controls like web application firewalls (WAFs) can provide additional protection by detecting and blocking injection attempts. Continuous monitoring and incident response readiness are also critical to detect potential exploitation attempts.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Dec 2025, 04:07 UTC

Technical details

References

Community reviews

Related threats