CVE-2025-14622

7.3 HIGH

📋 TL;DR

This SQL injection vulnerability in code-projects Student File Management System 1.0 allows attackers to execute arbitrary SQL commands through the firstname parameter in /admin/save_user.php. The vulnerability can be exploited remotely without authentication, potentially leading to data theft, modification, or system compromise. All users running version 1.0 of this software are affected.

💻 Affected Systems

Products:
  • code-projects Student File Management System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in the default installation and requires no special configuration to be exploitable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including sensitive student data theft, administrative account takeover, and potential remote code execution on the underlying server.

🟠

Likely Case

Unauthorized access to student records, grade manipulation, user account creation/deletion, and potential privilege escalation to admin access.

🟢

If Mitigated

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

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

The exploit has been publicly released and requires minimal technical skill to execute.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

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

Restart Required: No

Instructions:

No official patch available. Consider implementing input validation and parameterized queries in /admin/save_user.php or migrating to alternative software.

🔧 Temporary Workarounds

Web Application Firewall (WAF)

all

Deploy a WAF with SQL injection protection rules to block malicious requests to /admin/save_user.php

Input Validation Filter

all

Add server-side input validation to sanitize the firstname parameter before processing

// Example PHP validation
$firstname = filter_var($_POST['firstname'], FILTER_SANITIZE_STRING);
$firstname = mysqli_real_escape_string($connection, $firstname);

🧯 If You Can't Patch

  • Disable or restrict access to /admin/save_user.php via web server configuration
  • Implement network segmentation to isolate the vulnerable system from sensitive data

🔍 How to Verify

Check if Vulnerable:

Test the /admin/save_user.php endpoint with SQL injection payloads in the firstname parameter and observe database errors or unexpected behavior.

Check Version:

Check the software version in the application interface or configuration files

Verify Fix Applied:

After implementing fixes, test with the same SQL injection payloads to confirm they are properly blocked or sanitized.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL syntax in POST parameters to /admin/save_user.php
  • Multiple failed login attempts followed by SQL errors
  • Database error messages containing SQL fragments

Network Indicators:

  • HTTP POST requests to /admin/save_user.php with SQL keywords in parameters
  • Unusual database connection patterns from web server

SIEM Query:

source="web_logs" AND uri="/admin/save_user.php" AND (param="firstname" AND value MATCHES "(?i)(union|select|insert|update|delete|drop|--|#|;)")

🔗 References

📤 Share & Export