CVE-2025-3205

6.3 MEDIUM

📋 TL;DR

A critical SQL injection vulnerability in CodeAstro Student Grading System 1.0 allows remote attackers to execute arbitrary SQL commands via the studentId parameter in studentsubject.php. This affects all deployments of version 1.0, potentially compromising database integrity and confidentiality.

💻 Affected Systems

Products:
  • CodeAstro Student Grading System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: All installations of version 1.0 are vulnerable. The vulnerability exists in the default configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, modification, deletion, or potential remote code execution if database functions allow it.

🟠

Likely Case

Unauthorized data access, privilege escalation, and data manipulation affecting student records and system functionality.

🟢

If Mitigated

Limited impact with proper input validation and database permissions restricting damage to non-critical data.

🌐 Internet-Facing: HIGH - Remote exploitation possible without authentication, making internet-facing instances immediately vulnerable.
🏢 Internal Only: MEDIUM - Internal attackers or compromised internal systems could exploit this vulnerability.

🎯 Exploit Status

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

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

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://codeastro.com/

Restart Required: No

Instructions:

No official patch available. Consider upgrading to a newer version if available, or implement workarounds.

🔧 Temporary Workarounds

Input Validation and Parameterized Queries

all

Implement proper input validation and use parameterized queries/prepared statements for the studentId parameter.

Web Application Firewall (WAF)

all

Deploy a WAF with SQL injection protection rules to block exploitation attempts.

🧯 If You Can't Patch

  • Isolate the system from internet access and restrict internal network access
  • Implement strict database permissions and monitor for unusual SQL queries

🔍 How to Verify

Check if Vulnerable:

Test the studentsubject.php endpoint with SQL injection payloads in the studentId parameter. Check application version in admin panel or source files.

Check Version:

Check admin panel or look for version information in application files/configurations.

Verify Fix Applied:

Verify that SQL injection payloads no longer execute and that parameterized queries are implemented in studentsubject.php.

📡 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 studentsubject.php with SQL injection patterns in parameters

SIEM Query:

source="web_server" AND uri="*studentsubject.php*" AND (param="*studentId=*'*" OR param="*studentId=*;*" OR param="*studentId=*--*")

🔗 References

📤 Share & Export