CVE-2025-0788

6.3 MEDIUM

📋 TL;DR

This critical SQL injection vulnerability in ESAFENET CDG V5 allows remote attackers to execute arbitrary SQL commands via the 'id' parameter in the /content_top.jsp file. This could lead to data theft, modification, or deletion. All systems running the affected software with this endpoint exposed are at risk.

💻 Affected Systems

Products:
  • ESAFENET CDG V5
Versions: Unknown specific versions, but all V5 versions with vulnerable /content_top.jsp file
Operating Systems: All platforms running the software
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability exists in default installation. Requires the /content_top.jsp endpoint to be accessible.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data exfiltration, privilege escalation, or system takeover via SQL injection to RCE chaining.

🟠

Likely Case

Unauthorized database access allowing data theft, manipulation of application data, or potential authentication bypass.

🟢

If Mitigated

Limited impact with proper input validation, WAF rules, and database permissions restricting damage to non-critical data.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit details publicly available on GitHub. Simple SQL injection via URL parameter manipulation.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available

Restart Required: No

Instructions:

No official patch available. Vendor did not respond to disclosure. Consider workarounds or alternative solutions.

🔧 Temporary Workarounds

WAF Rule Implementation

all

Deploy web application firewall rules to block SQL injection patterns targeting the /content_top.jsp endpoint

Endpoint Restriction

all

Block access to /content_top.jsp at network or application level if not required

🧯 If You Can't Patch

  • Implement strict input validation and parameterized queries in the application code
  • Apply network segmentation to isolate vulnerable systems and restrict database access

🔍 How to Verify

Check if Vulnerable:

Test /content_top.jsp endpoint with SQL injection payloads in the 'id' parameter (e.g., id=1' OR '1'='1)

Check Version:

Check application version through admin interface or configuration files

Verify Fix Applied:

Verify SQL injection attempts no longer succeed and return appropriate error handling

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL error messages in application logs
  • Multiple requests to /content_top.jsp with SQL keywords in parameters

Network Indicators:

  • HTTP requests containing SQL injection patterns targeting /content_top.jsp

SIEM Query:

source="web_logs" AND uri="/content_top.jsp" AND (param="id" AND value MATCHES "(?i)(union|select|insert|update|delete|drop|exec|--|#|;)")

🔗 References

📤 Share & Export