CVE-2025-14619

7.3 HIGH

📋 TL;DR

This vulnerability allows remote attackers to execute SQL injection attacks via the 'stud_no' parameter in the login_query.php file of Student File Management System 1.0. Attackers can potentially access, modify, or delete database content without authentication. All users running this specific version of the software are affected.

💻 Affected Systems

Products:
  • Student File Management System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in the default installation. Any system with login_query.php accessible is vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data manipulation, authentication bypass, and potential server takeover via SQL injection leading to remote code execution.

🟠

Likely Case

Unauthorized access to student records, grade manipulation, personal information theft, and potential privilege escalation within the application.

🟢

If Mitigated

Limited impact with proper input validation and database permissions, potentially only error messages or partial data exposure.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

The exploit is publicly available and requires minimal technical skill to execute. Remote exploitation without authentication makes this particularly dangerous.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

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

Restart Required: No

Instructions:

1. Check vendor website for updates
2. If no patch available, implement workarounds
3. Consider replacing with alternative software

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Add parameterized queries and input validation to login_query.php

Modify login_query.php to use prepared statements with PDO or mysqli

Web Application Firewall

all

Deploy WAF with SQL injection protection rules

Configure WAF to block SQL injection patterns

🧯 If You Can't Patch

  • Isolate the system behind a firewall with strict access controls
  • Implement network segmentation to limit database access

🔍 How to Verify

Check if Vulnerable:

Test login_query.php with SQL injection payloads in stud_no parameter

Check Version:

Check software version in admin panel or configuration files

Verify Fix Applied:

Test with SQL injection payloads and verify they're blocked or sanitized

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts with SQL patterns
  • Error messages containing SQL syntax

Network Indicators:

  • HTTP requests with SQL keywords in parameters
  • Unusual traffic patterns to login_query.php

SIEM Query:

source="web_logs" AND (uri="*login_query.php*" AND (param="*stud_no*" AND value="*UNION*" OR value="*SELECT*" OR value="*OR 1=1*"))

🔗 References

📤 Share & Export