CVE-2025-13585

7.3 HIGH

📋 TL;DR

CVE-2025-13585 is a SQL injection vulnerability in itsourcecode COVID Tracking System 1.0 that allows attackers to execute arbitrary SQL commands via the 'code' parameter in /login.php. This affects all deployments of this specific software version. Attackers can potentially access, modify, or delete database content remotely.

💻 Affected Systems

Products:
  • itsourcecode COVID Tracking System
Versions: 1.0
Operating Systems: Any OS running PHP with database backend
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all installations of version 1.0. The vulnerability is in the core login functionality.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including sensitive health data exfiltration, authentication bypass, system takeover, and potential ransomware deployment.

🟠

Likely Case

Unauthorized data access, credential theft, and potential privilege escalation leading to system compromise.

🟢

If Mitigated

Limited impact with proper input validation, WAF protection, and database permission restrictions.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit is publicly available and targets the login page directly without authentication.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://itsourcecode.com/

Restart Required: No

Instructions:

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

🔧 Temporary Workarounds

WAF Rule Implementation

all

Deploy web application firewall rules to block SQL injection patterns in the 'code' parameter

# Example ModSecurity rule: SecRule ARGS:code "@detectSQLi" "id:1001,phase:2,deny,status:403"

Input Validation Filter

all

Add parameter validation in login.php to sanitize 'code' input

# PHP example: $code = mysqli_real_escape_string($conn, $_POST['code']);

🧯 If You Can't Patch

  • Isolate the system behind a reverse proxy with strict input validation
  • Implement network segmentation and restrict database access to minimum required connections

🔍 How to Verify

Check if Vulnerable:

Test /login.php with SQL injection payloads in the 'code' parameter (e.g., ' OR '1'='1)

Check Version:

Check software version in admin panel or configuration files

Verify Fix Applied:

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

📡 Detection & Monitoring

Log Indicators:

  • Multiple failed login attempts with SQL patterns in parameters
  • Unusual database queries from web server IP

Network Indicators:

  • HTTP POST requests to /login.php with SQL keywords in parameters
  • Unusual outbound database connections

SIEM Query:

source="web_logs" AND uri_path="/login.php" AND (param="code" AND value MATCHES "(?i)(union|select|insert|delete|update|drop|or|and)")

🔗 References

📤 Share & Export