CVE-2024-11096

6.3 MEDIUM

📋 TL;DR

This critical SQL injection vulnerability in code-projects Task Manager 1.0 allows remote attackers to execute arbitrary SQL commands via the projectName parameter in /newProject.php. Attackers can potentially read, modify, or delete database content. All users running Task Manager 1.0 with the vulnerable component exposed are affected.

💻 Affected Systems

Products:
  • code-projects Task Manager
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability exists in the default installation when /newProject.php is accessible.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data destruction, and potential remote code execution if database permissions allow.

🟠

Likely Case

Unauthorized data access, data manipulation, and potential privilege escalation within the application.

🟢

If Mitigated

Limited impact with proper input validation and database permission restrictions 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 on GitHub, making this easily exploitable by attackers.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

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

Restart Required: No

Instructions:

No official patch available. Consider implementing workarounds or migrating to alternative software.

🔧 Temporary Workarounds

Input Validation Filter

all

Add input validation to sanitize projectName parameter before processing

Modify /newProject.php to include parameter validation: $projectName = mysqli_real_escape_string($connection, $_POST['projectName']);

Web Application Firewall

all

Deploy WAF with SQL injection protection rules

🧯 If You Can't Patch

  • Restrict access to /newProject.php using network ACLs or authentication
  • Implement database user with minimal permissions (read-only where possible)

🔍 How to Verify

Check if Vulnerable:

Test /newProject.php endpoint with SQL injection payloads in projectName parameter

Check Version:

Check application version in admin panel or configuration files

Verify Fix Applied:

Attempt SQL injection after implementing fixes and verify no database errors or unexpected behavior

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts following SQL errors
  • Requests to /newProject.php with SQL keywords in parameters

Network Indicators:

  • HTTP POST requests to /newProject.php containing SQL injection patterns
  • Unusual database connection patterns from web server

SIEM Query:

source="web_logs" AND uri="/newProject.php" AND (request CONTAINS "UNION" OR request CONTAINS "SELECT" OR request CONTAINS "INSERT" OR request CONTAINS "DELETE")

🔗 References

📤 Share & Export