CVE-2025-13241

7.3 HIGH

📋 TL;DR

CVE-2025-13241 is an SQL injection vulnerability in code-projects Student Information System 2.0 that allows remote attackers to execute arbitrary SQL commands via the Username parameter in /index.php. This affects all deployments of the vulnerable software version. Successful exploitation could lead to data theft, modification, or complete system compromise.

💻 Affected Systems

Products:
  • code-projects Student Information System
Versions: 2.0
Operating Systems: Any OS running PHP and MySQL/MariaDB
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all installations of version 2.0 with default configuration. Requires PHP and database backend.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data exfiltration, privilege escalation, and potential remote code execution on the underlying server.

🟠

Likely Case

Unauthorized access to student records, grades, personal information, and potential modification of academic data.

🟢

If Mitigated

Limited impact with proper input validation and database permissions, potentially only allowing data viewing without modification.

🌐 Internet-Facing: HIGH - The vulnerability is remotely exploitable and affects a web application component.
🏢 Internal Only: MEDIUM - Internal attackers could still exploit this, but external threat actors pose greater risk.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploit details are publicly available on GitHub, making this easily weaponizable by attackers with basic SQL injection knowledge.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://code-projects.org/

Restart Required: No

Instructions:

No official patch available. Check vendor website for updates. Consider implementing parameterized queries and input validation in /index.php.

🔧 Temporary Workarounds

Web Application Firewall (WAF)

all

Deploy a WAF with SQL injection protection rules to block malicious payloads.

Input Validation Filter

all

Add input validation to sanitize Username parameter before processing.

// PHP example: $username = mysqli_real_escape_string($conn, $_POST['Username']);

🧯 If You Can't Patch

  • Isolate the system from internet access and restrict to internal network only.
  • Implement strict network segmentation and monitor all database queries for suspicious patterns.

🔍 How to Verify

Check if Vulnerable:

Test the Username parameter with SQL injection payloads like ' OR '1'='1 and observe database errors or unexpected behavior.

Check Version:

Check application version in admin panel or review source code for version identifiers.

Verify Fix Applied:

Test with same payloads after implementing fixes - should return proper error messages or reject malicious input.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL syntax errors in application logs
  • Multiple failed login attempts with SQL-like patterns in Username field

Network Indicators:

  • HTTP requests containing SQL keywords in Username parameter
  • Unusual database query patterns from web server

SIEM Query:

source="web_logs" AND (Username="*' OR*" OR Username="*UNION*" OR Username="*SELECT*" OR Username="*--*" OR Username="*;*" OR Username="*/*")

🔗 References

📤 Share & Export