CVE-2025-4738

9.8 CRITICAL

📋 TL;DR

This SQL injection vulnerability in Yirmibes Software MY ERP allows attackers to execute arbitrary SQL commands through unvalidated user input. It affects all MY ERP installations before version 1.170. Attackers could potentially access, modify, or delete database content.

💻 Affected Systems

Products:
  • Yirmibes Software MY ERP
Versions: All versions before 1.170
Operating Systems: All platforms running MY ERP
Default Config Vulnerable: ⚠️ Yes
Notes: All installations with default configurations are vulnerable. The vulnerability exists in the application code itself.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, data destruction, authentication bypass, and potential remote code execution via database functions.

🟠

Likely Case

Unauthorized data access, privilege escalation, and data manipulation affecting business operations and confidentiality.

🟢

If Mitigated

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

🌐 Internet-Facing: HIGH
🏢 Internal Only: HIGH

🎯 Exploit Status

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

SQL injection vulnerabilities are typically easy to exploit with basic tools. The CVE description suggests improper input neutralization, indicating straightforward exploitation.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 1.170 or later

Vendor Advisory: https://www.usom.gov.tr/bildirim/tr-25-0132

Restart Required: Yes

Instructions:

1. Download MY ERP version 1.170 or later from official vendor sources. 2. Backup current installation and database. 3. Apply the update following vendor instructions. 4. Restart the application service. 5. Verify successful update.

🔧 Temporary Workarounds

Web Application Firewall (WAF)

all

Deploy a WAF with SQL injection protection rules to block malicious requests.

Input Validation Filter

all

Implement application-level input validation to reject SQL special characters.

🧯 If You Can't Patch

  • Isolate the MY ERP system from untrusted networks using network segmentation.
  • Implement strict database user permissions with least privilege principle.

🔍 How to Verify

Check if Vulnerable:

Check MY ERP version in administration panel or configuration files. If version is below 1.170, system is vulnerable.

Check Version:

Check application configuration or admin interface for version information.

Verify Fix Applied:

Confirm version is 1.170 or higher in administration panel and test SQL injection attempts are blocked.

📡 Detection & Monitoring

Log Indicators:

  • Unusual database query patterns
  • SQL syntax errors in application logs
  • Multiple failed login attempts with SQL characters

Network Indicators:

  • HTTP requests containing SQL keywords (SELECT, UNION, INSERT, etc.)
  • Unusual database port traffic

SIEM Query:

source="myerp_logs" AND ("sql" OR "union" OR "select" OR "insert" OR "' OR '1'='1")

🔗 References

📤 Share & Export