CVE-2025-11343VulnerabilityPublished 6 Oct 2025

CVE-2025-11343: code-projects Student Crud Operation · SQL Injection

Affects code-projects Student Crud OperationSource 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 35% 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 6 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
code-projects Student Crud Operation	Affected =3.3	Fixed in–

AI-suggested

European organizations should immediately implement the following specific mitigations: 1) Apply input validation and sanitization on all user-supplied parameters, especially the 'ID' parameter in delete.php, to prevent SQL injection. 2) Refactor database queries to use parameterized statements or prepared queries rather than dynamic SQL concatenation. 3) Restrict database user permissions to the minimum necessary to limit the impact of potential injection attacks. 4) Monitor database and application logs for unusual query patterns or repeated failed attempts targeting the 'ID' parameter. 5) If official patches become available, prioritize their deployment in all affected environments. 6) Conduct a thorough code review of similar CRUD operations within the application to identify and remediate other injection points. 7) Implement Web Application Firewall (WAF) rules to detect and block SQL injection attempts targeting this endpoint. 8) Educate developers and administrators on secure coding practices and the importance of input validation. 9) Regularly back up databases and verify backup integrity to enable recovery in case of data tampering or deletion. 10) Consider isolating or segmenting the affected application environment to reduce lateral movement risk if exploited.

Description

A security vulnerability has been detected in code-projects Student Crud Operation 3.3. Affected is an unknown function of the file delete.php. The manipulation of the argument 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

For European organizations, especially educational institutions and administrative bodies using the Student Crud Operation 3.3 application, this vulnerability poses a significant risk to the confidentiality and integrity of student and administrative data. Successful exploitation could lead to unauthorized disclosure of personal data, violating GDPR and other data protection regulations, resulting in legal and financial penalties. Data manipulation or deletion could disrupt critical academic and administrative processes, impacting availability and operational continuity. The remote, unauthenticated nature of the attack vector increases the threat surface, potentially allowing attackers to compromise systems without insider access. This risk is heightened in countries with widespread adoption of this software or similar platforms, where sensitive student information is processed and stored. Additionally, reputational damage from data breaches could affect trust in affected institutions. The medium severity rating suggests that while the vulnerability is serious, it may not lead to full system compromise but still requires urgent attention to prevent exploitation.

Summary

CVE-2025-11343 identifies a SQL injection vulnerability in the Student Crud Operation 3.3 application developed by code-projects. The flaw exists in the delete.php script, where the 'ID' parameter is not properly sanitized or validated before being used in SQL queries. This allows an unauthenticated remote attacker to inject arbitrary SQL commands, potentially manipulating the backend database. The vulnerability does not require user interaction or privileges, making it easier to exploit remotely over the network. The CVSS 4.0 base score is 6.9 (medium), reflecting the moderate impact on confidentiality, integrity, and availability, with low complexity and no authentication required. Exploiting this vulnerability could enable attackers to read, modify, or delete sensitive student records or other data stored in the database, leading to data breaches or service disruptions. Although no public exploit code is currently known to be actively used, the public disclosure increases the likelihood of future exploitation attempts. The vulnerability affects only version 3.3 of the product, and no official patches have been linked yet, emphasizing the need for immediate mitigation. This vulnerability is particularly relevant for educational institutions or organizations managing student data using this software or similar CRUD applications.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Oct 2025, 18:17 UTC

Technical details

References

Community reviews

Related threats