CVE-2025-3707

6.5 MEDIUM

📋 TL;DR

The eHDR CTMS from Sunnet contains a SQL injection vulnerability that allows authenticated users with regular privileges to execute arbitrary SQL commands and read database contents. This affects organizations using the vulnerable eHDR CTMS software for clinical trial management.

💻 Affected Systems

Products:
  • Sunnet eHDR CTMS
Versions: Specific versions not disclosed in available references
Operating Systems: Not specified
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability exists in default configuration; requires regular user privileges for exploitation

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could extract sensitive clinical trial data, patient information, and administrative credentials, potentially leading to data breach, regulatory violations, and system compromise.

🟠

Likely Case

Attackers with regular user access could read database tables containing clinical trial data, user information, and system configuration details.

🟢

If Mitigated

With proper input validation and parameterized queries, SQL injection would be prevented, limiting database access to authorized queries only.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Requires authenticated access but SQL injection is typically straightforward to exploit with basic tools

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Not specified in available references

Vendor Advisory: https://www.twcert.org.tw/en/cp-139-10084-d7c47-2.html

Restart Required: Yes

Instructions:

1. Contact Sunnet for patch information
2. Apply the security update provided by the vendor
3. Restart the eHDR CTMS application
4. Verify the fix by testing for SQL injection

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement server-side input validation and parameterized queries to prevent SQL injection

Web Application Firewall

all

Deploy WAF with SQL injection protection rules

🧯 If You Can't Patch

  • Implement network segmentation to isolate the CTMS system
  • Apply principle of least privilege to database accounts

🔍 How to Verify

Check if Vulnerable:

Test user input fields for SQL injection using safe testing methods or contact vendor for vulnerability assessment

Check Version:

Check application version through admin interface or contact vendor

Verify Fix Applied:

Perform SQL injection testing on patched system and verify database queries are properly parameterized

📡 Detection & Monitoring

Log Indicators:

  • Unusual database query patterns
  • Multiple failed login attempts followed by SQL-like queries
  • Database error messages containing SQL syntax

Network Indicators:

  • Unusual SQL query patterns in application traffic
  • Requests with SQL keywords in parameters

SIEM Query:

source="web_server" AND (event_type="sql_error" OR message="*sql*" OR message="*database*" OR parameters="*SELECT*" OR parameters="*UNION*")

🔗 References

📤 Share & Export