CVE-2023-26568

9.8 CRITICAL

📋 TL;DR

Unauthenticated attackers can execute arbitrary SQL queries against IDAttend's IDWeb application, potentially extracting or modifying all database data. This affects all users running IDWeb version 3.1.052 or earlier. The vulnerability is particularly dangerous because it requires no authentication.

💻 Affected Systems

Products:
  • IDAttend IDWeb
Versions: 3.1.052 and earlier
Operating Systems: Windows
Default Config Vulnerable: ⚠️ Yes
Notes: All deployments with the vulnerable version are affected regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data destruction, and potential lateral movement to other systems via database connections.

🟠

Likely Case

Data exfiltration of sensitive student/attendance information, potential credential harvesting, and data manipulation.

🟢

If Mitigated

Limited impact with proper network segmentation, database permissions, and monitoring in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: HIGH

🎯 Exploit Status

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

SQL injection vulnerabilities are commonly exploited and this one requires no authentication, making it highly attractive to attackers.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 3.1.053 or later

Vendor Advisory: https://www.themissinglink.com.au/security-advisories/cve-2023-26568

Restart Required: Yes

Instructions:

1. Download latest version from IDAttend vendor. 2. Backup current installation and database. 3. Install updated version. 4. Restart application services. 5. Verify functionality.

🔧 Temporary Workarounds

Network Segmentation

all

Restrict access to IDWeb application to authorized internal networks only

Web Application Firewall

all

Deploy WAF with SQL injection protection rules

🧯 If You Can't Patch

  • Implement strict network access controls to limit who can reach the IDWeb application
  • Deploy database monitoring to detect unusual SQL queries and implement database-level access restrictions

🔍 How to Verify

Check if Vulnerable:

Check IDWeb application version in admin interface or application files. If version is 3.1.052 or earlier, system is vulnerable.

Check Version:

Check application web interface or examine application files for version information

Verify Fix Applied:

Confirm version is 3.1.053 or later and test that GetStudentGroupStudents endpoint properly validates input.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL error messages in application logs
  • Multiple failed authentication attempts followed by SQL queries
  • Unusual database query patterns from application user

Network Indicators:

  • SQL syntax in HTTP GET/POST parameters to IDWeb endpoints
  • Unusual traffic patterns to GetStudentGroupStudents method

SIEM Query:

source="idweb.log" AND ("sql" OR "syntax" OR "injection")

🔗 References

📤 Share & Export