CVE-2025-5119

7.3 HIGH

📋 TL;DR

This critical SQL injection vulnerability in Emlog Pro allows remote attackers to manipulate database queries through the 'tag' parameter in api_controller.php. Successful exploitation could lead to data theft, modification, or deletion. All users running Emlog Pro 2.5.11 are affected.

💻 Affected Systems

Products:
  • Emlog Pro
Versions: 2.5.11
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Any installation with the vulnerable file accessible via web interface is affected.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data exfiltration, privilege escalation, and potential remote code execution via database functions.

🟠

Likely Case

Unauthorized data access, modification of content, and potential administrative account takeover.

🟢

If Mitigated

Limited impact with proper input validation and database permission restrictions in place.

🌐 Internet-Facing: HIGH - Remote exploitation without authentication makes internet-facing instances extremely vulnerable.
🏢 Internal Only: MEDIUM - Internal instances still vulnerable but attack surface is reduced.

🎯 Exploit Status

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

Public exploit details available on GitHub, making exploitation straightforward for attackers.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: Not available

Restart Required: No

Instructions:

1. Monitor vendor for official patch. 2. Consider upgrading to latest version if available. 3. Apply workarounds immediately.

🔧 Temporary Workarounds

Input Validation Filter

all

Add input validation for the 'tag' parameter in api_controller.php

Modify /include/controller/api_controller.php to sanitize tag parameter input

WAF Rule

all

Implement web application firewall rules to block SQL injection patterns

Add WAF rule: Detect and block SQL injection attempts on tag parameter

🧯 If You Can't Patch

  • Restrict access to /include/controller/api_controller.php via web server configuration
  • Implement network segmentation to isolate Emlog Pro instances from sensitive systems

🔍 How to Verify

Check if Vulnerable:

Check if /include/controller/api_controller.php exists and contains vulnerable code for tag parameter handling.

Check Version:

Check Emlog Pro version in admin panel or via version file.

Verify Fix Applied:

Test SQL injection attempts against the tag parameter to confirm they are blocked.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts after SQL injection attempts
  • Unexpected parameter values in web server logs for tag parameter

Network Indicators:

  • SQL injection payloads in HTTP requests to api_controller.php
  • Unusual database connection patterns from web server

SIEM Query:

source="web_logs" AND uri="/include/controller/api_controller.php" AND (tag CONTAINS "'" OR tag CONTAINS "--" OR tag CONTAINS "UNION")

🔗 References

📤 Share & Export