CVE-2026-2171

7.3 HIGH

📋 TL;DR

This SQL injection vulnerability in Online Student Management System 1.0 allows attackers to manipulate database queries through the login form. Attackers can potentially access, modify, or delete sensitive student data. All deployments of version 1.0 with default configurations are affected.

💻 Affected Systems

Products:
  • code-projects Online Student Management System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the login component at accounts.php with username/password parameters

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, data destruction, or full system takeover via SQL injection to RCE chaining

🟠

Likely Case

Unauthorized access to student records, grade manipulation, or credential theft

🟢

If Mitigated

Limited impact with proper input validation and database permissions

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Remote exploitation possible via login form; exploit details are publicly available

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

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

Restart Required: No

Instructions:

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

🔧 Temporary Workarounds

Input Validation Filter

all

Add parameterized queries or input validation to accounts.php

Modify accounts.php to use prepared statements: $stmt = $conn->prepare('SELECT * FROM users WHERE username = ? AND password = ?'); $stmt->bind_param('ss', $username, $password);

Web Application Firewall

linux

Deploy WAF with SQL injection rules

Install and configure ModSecurity with OWASP CRS rules

🧯 If You Can't Patch

  • Isolate the system behind a reverse proxy with strict input filtering
  • Implement network segmentation and restrict database access to application server only

🔍 How to Verify

Check if Vulnerable:

Test login form with SQL injection payloads like ' OR '1'='1 in username/password fields

Check Version:

Check system documentation or about page for version information

Verify Fix Applied:

Attempt SQL injection after implementing parameterized queries; successful login should only occur with valid credentials

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL errors in application logs
  • Multiple failed login attempts with SQL syntax

Network Indicators:

  • HTTP POST requests to accounts.php containing SQL keywords
  • Unusual database connection patterns

SIEM Query:

source="web_logs" AND uri="/accounts.php" AND (request_body CONTAINS "' OR" OR request_body CONTAINS "UNION" OR request_body CONTAINS "SELECT *")

🔗 References

📤 Share & Export