CVE-2025-14640

7.3 HIGH

📋 TL;DR

This vulnerability allows remote attackers to execute SQL injection attacks against the Student File Management System 1.0 by manipulating the stud_no parameter in the /admin/save_student.php file. This can lead to unauthorized database access, data theft, or system compromise. Organizations using this specific software version 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; requires the /admin/save_student.php endpoint to be accessible.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise allowing data exfiltration, modification, or deletion; potential system takeover via SQL injection leading to remote code execution.

🟠

Likely Case

Unauthorized access to student records, personal data theft, database manipulation, and potential privilege escalation.

🟢

If Mitigated

Limited impact with proper input validation, parameterized queries, and network segmentation in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit details are publicly available; SQL injection via stud_no parameter is straightforward.

🛠️ 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 the save_student.php file.

🔧 Temporary Workarounds

Web Application Firewall (WAF)

all

Deploy a WAF with SQL injection rules to block malicious requests.

Input Validation

all

Implement server-side validation for stud_no parameter to allow only expected characters.

🧯 If You Can't Patch

  • Restrict network access to the /admin/save_student.php endpoint using firewall rules.
  • Implement database user with minimal privileges for the application.

🔍 How to Verify

Check if Vulnerable:

Test the /admin/save_student.php endpoint with SQL injection payloads in the stud_no parameter.

Check Version:

Check the software version in the application interface or configuration files.

Verify Fix Applied:

Verify that SQL injection attempts no longer succeed and proper input validation is implemented.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts or parameter manipulation in web server logs

Network Indicators:

  • HTTP requests to /admin/save_student.php with SQL keywords in parameters

SIEM Query:

source="web_server" AND uri="/admin/save_student.php" AND (param="stud_no" AND value CONTAINS "UNION" OR value CONTAINS "SELECT" OR value CONTAINS "OR 1=1")

🔗 References

📤 Share & Export