CVE-2025-10102

7.3 HIGH

📋 TL;DR

CVE-2025-10102 is a SQL injection vulnerability in code-projects Online Event Judging System 1.0 that allows remote attackers to execute arbitrary SQL commands via the Username parameter in /index.php. This affects all deployments of version 1.0, potentially compromising database integrity and confidentiality. Attackers can exploit this without authentication to steal, modify, or delete data.

💻 Affected Systems

Products:
  • code-projects Online Event Judging System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: All installations of version 1.0 are vulnerable. No specific configuration changes mitigate this vulnerability.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, data destruction, or full system takeover via subsequent attacks.

🟠

Likely Case

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

🟢

If Mitigated

Limited impact with proper input validation and database permissions, though risk remains if vulnerable code is exposed.

🌐 Internet-Facing: HIGH - Remote exploitation without authentication makes internet-facing instances extremely vulnerable.
🏢 Internal Only: MEDIUM - Internal instances are still vulnerable but require network access, reducing exposure surface.

🎯 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 with basic SQL injection knowledge.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

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

Restart Required: No

Instructions:

No official patch available. Consider implementing input validation and parameterized queries as workarounds, or replace with a secure alternative.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement server-side validation to reject malicious input in Username parameter

Modify /index.php to validate Username input against allowed character patterns

Web Application Firewall (WAF) Rules

all

Deploy WAF rules to block SQL injection patterns in Username parameter

Add WAF rule: Detect and block SQL keywords in Username parameter

🧯 If You Can't Patch

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

🔍 How to Verify

Check if Vulnerable:

Test the Username parameter in /index.php with SQL injection payloads like ' OR '1'='1

Check Version:

Check application version in admin panel or configuration files

Verify Fix Applied:

Verify that SQL injection attempts no longer succeed and return appropriate error messages

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL error messages in application logs
  • Multiple failed login attempts with SQL patterns

Network Indicators:

  • HTTP requests to /index.php containing SQL keywords in Username parameter

SIEM Query:

source="web_logs" AND uri="/index.php" AND (Username CONTAINS "' OR" OR Username CONTAINS "UNION" OR Username CONTAINS "SELECT")

🔗 References

📤 Share & Export