CVE-2025-13241: SQL Injection in code-projects Student Information System
A flaw has been found in code-projects Student Information System 2.0. This vulnerability affects unknown code of the file /index.php. Executing manipulation of the argument Username can lead to sql injection. The attack can be executed remotely. The exploit has been published and may be used.
AI Analysis
Technical Summary
CVE-2025-13241 is a SQL injection vulnerability identified in the code-projects Student Information System version 2.0, specifically within the /index.php file. The vulnerability arises from improper sanitization of the 'Username' parameter, which can be manipulated by remote attackers to inject arbitrary SQL queries. This flaw allows attackers to execute unauthorized SQL commands on the backend database, potentially leading to unauthorized data disclosure, modification, or deletion. The vulnerability is remotely exploitable without requiring authentication or user interaction, increasing its risk profile. The CVSS 4.0 base score is 6.9 (medium severity), reflecting the network attack vector, low attack complexity, and no privileges or user interaction needed. Although no known exploits are currently active in the wild, a public exploit has been published, which could facilitate exploitation by threat actors. The vulnerability affects only version 2.0 of the Student Information System, and no official patches have been linked yet. The lack of secure coding practices around input validation and parameterized queries in the affected file is the root cause. This vulnerability could allow attackers to bypass authentication, extract sensitive student data, or corrupt the database, impacting confidentiality, integrity, and availability of the system.
Potential Impact
For European organizations, particularly educational institutions using the code-projects Student Information System 2.0, this vulnerability poses a significant risk to the confidentiality and integrity of sensitive student data. Exploitation could lead to unauthorized disclosure of personal information, academic records, and potentially financial data. Data integrity could be compromised through unauthorized modifications or deletions, disrupting academic operations and trust. Availability may also be affected if attackers execute destructive SQL commands or cause database corruption. The remote, unauthenticated nature of the exploit increases the likelihood of attacks, especially in environments with internet-facing Student Information System portals. This could result in regulatory compliance violations under GDPR due to data breaches, leading to legal and financial repercussions. The publication of a public exploit increases the urgency for European organizations to address this vulnerability promptly to avoid potential targeted attacks or opportunistic exploitation.
Mitigation Recommendations
1. Monitor for official patches or updates from code-projects and apply them immediately once available. 2. Until patches are released, implement strict input validation and sanitization on the 'Username' parameter to block malicious SQL payloads. 3. Employ parameterized queries or prepared statements in the application code to prevent SQL injection. 4. Deploy a Web Application Firewall (WAF) with rules specifically designed to detect and block SQL injection attempts targeting the Student Information System. 5. Conduct regular security assessments and penetration testing focused on injection vulnerabilities. 6. Restrict database user permissions to the minimum necessary to limit the impact of a potential injection attack. 7. Monitor logs for unusual database queries or failed login attempts that could indicate exploitation attempts. 8. Educate IT staff and administrators about the vulnerability and signs of exploitation to enable rapid response. 9. Isolate the Student Information System from direct internet exposure where possible, using VPNs or secure access gateways. 10. Maintain regular backups of the database to enable recovery in case of data corruption or loss.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands
CVE-2025-13241: SQL Injection in code-projects Student Information System
Description
A flaw has been found in code-projects Student Information System 2.0. This vulnerability affects unknown code of the file /index.php. Executing manipulation of the argument Username can lead to sql injection. The attack can be executed remotely. The exploit has been published and may be used.
AI-Powered Analysis
Technical Analysis
CVE-2025-13241 is a SQL injection vulnerability identified in the code-projects Student Information System version 2.0, specifically within the /index.php file. The vulnerability arises from improper sanitization of the 'Username' parameter, which can be manipulated by remote attackers to inject arbitrary SQL queries. This flaw allows attackers to execute unauthorized SQL commands on the backend database, potentially leading to unauthorized data disclosure, modification, or deletion. The vulnerability is remotely exploitable without requiring authentication or user interaction, increasing its risk profile. The CVSS 4.0 base score is 6.9 (medium severity), reflecting the network attack vector, low attack complexity, and no privileges or user interaction needed. Although no known exploits are currently active in the wild, a public exploit has been published, which could facilitate exploitation by threat actors. The vulnerability affects only version 2.0 of the Student Information System, and no official patches have been linked yet. The lack of secure coding practices around input validation and parameterized queries in the affected file is the root cause. This vulnerability could allow attackers to bypass authentication, extract sensitive student data, or corrupt the database, impacting confidentiality, integrity, and availability of the system.
Potential Impact
For European organizations, particularly educational institutions using the code-projects Student Information System 2.0, this vulnerability poses a significant risk to the confidentiality and integrity of sensitive student data. Exploitation could lead to unauthorized disclosure of personal information, academic records, and potentially financial data. Data integrity could be compromised through unauthorized modifications or deletions, disrupting academic operations and trust. Availability may also be affected if attackers execute destructive SQL commands or cause database corruption. The remote, unauthenticated nature of the exploit increases the likelihood of attacks, especially in environments with internet-facing Student Information System portals. This could result in regulatory compliance violations under GDPR due to data breaches, leading to legal and financial repercussions. The publication of a public exploit increases the urgency for European organizations to address this vulnerability promptly to avoid potential targeted attacks or opportunistic exploitation.
Mitigation Recommendations
1. Monitor for official patches or updates from code-projects and apply them immediately once available. 2. Until patches are released, implement strict input validation and sanitization on the 'Username' parameter to block malicious SQL payloads. 3. Employ parameterized queries or prepared statements in the application code to prevent SQL injection. 4. Deploy a Web Application Firewall (WAF) with rules specifically designed to detect and block SQL injection attempts targeting the Student Information System. 5. Conduct regular security assessments and penetration testing focused on injection vulnerabilities. 6. Restrict database user permissions to the minimum necessary to limit the impact of a potential injection attack. 7. Monitor logs for unusual database queries or failed login attempts that could indicate exploitation attempts. 8. Educate IT staff and administrators about the vulnerability and signs of exploitation to enable rapid response. 9. Isolate the Student Information System from direct internet exposure where possible, using VPNs or secure access gateways. 10. Maintain regular backups of the database to enable recovery in case of data corruption or loss.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulDB
- Date Reserved
- 2025-11-15T06:57:14.297Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69197b67f90981bc0ff20957
Added to database: 11/16/2025, 7:21:11 AM
Last enriched: 11/16/2025, 7:28:45 AM
Last updated: 1/7/2026, 6:07:59 AM
Views: 74
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-14835: CWE-80 Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in opajaap WP Photo Album Plus
HighCVE-2026-0650: CWE-306 Missing Authentication for Critical Function in OpenFlagr Flagr
CriticalCVE-2025-15474: CWE-770 Allocation of Resources Without Limits or Throttling in AuntyFey AuntyFey Smart Combination Lock
MediumCVE-2025-14468: CWE-352 Cross-Site Request Forgery (CSRF) in mohammed_kaludi AMP for WP – Accelerated Mobile Pages
MediumCVE-2025-9611: CWE-749 Exposed Dangerous Method or Function in Microsoft Playwright
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.