CVE-2025-10418

6.3 MEDIUM

📋 TL;DR

This vulnerability allows remote attackers to execute SQL injection attacks against SourceCodester Student Grading System 1.0 via the ID parameter in /view_students.php. Attackers can potentially access, modify, or delete database content. Organizations using this specific software version are affected.

💻 Affected Systems

Products:
  • SourceCodester Student Grading System
Versions: 1.0
Operating Systems: Any
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects installations with the vulnerable /view_students.php file accessible.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including student records, grades, and potentially administrative credentials, leading to data theft, manipulation, or system takeover.

🟠

Likely Case

Unauthorized access to student data, grade manipulation, or extraction of sensitive information from the database.

🟢

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: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Public exploit available on GitHub, remote exploitation possible without authentication.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://www.sourcecodester.com/

Restart Required: No

Instructions:

No official patch available. Consider implementing input validation or parameterized queries in the source code.

🔧 Temporary Workarounds

Input Validation Filter

all

Add server-side validation to ensure ID parameter contains only numeric values

Modify /view_students.php to validate ID parameter with is_numeric() or similar

Web Application Firewall

all

Deploy WAF rules to block SQL injection patterns targeting the ID parameter

Configure WAF to block SQL injection patterns in query parameters

🧯 If You Can't Patch

  • Restrict network access to the application using firewall rules
  • Implement database user with minimal permissions (read-only if possible)

🔍 How to Verify

Check if Vulnerable:

Test /view_students.php with SQL injection payloads in ID parameter (e.g., ' OR '1'='1)

Check Version:

Check application version in admin panel or source code comments

Verify Fix Applied:

Test with same payloads after implementing fixes - should return error or no data

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL errors in application logs
  • Multiple requests to /view_students.php with suspicious parameters

Network Indicators:

  • SQL keywords in HTTP GET parameters
  • Unusual database query patterns

SIEM Query:

source="web_logs" AND uri="/view_students.php" AND (param="*sql*" OR param="*union*" OR param="*select*")

🔗 References

📤 Share & Export