CVE-2024-10119 — AI Deep Analysis Summary

Q: What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: OS Command Injection in SECOM WRTM326 Router. 🔥 **Consequences**: Attackers can execute **arbitrary system commands** remotely. Total compromise of the device is possible.

Q: Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **CWE-78** (OS Command Injection). ❌ **Flaw**: Specific parameters are **not properly validated**. Malicious input bypasses checks and runs as system commands.

Q: Who is affected? (Versions/Components)

📦 **Affected**: SECOM WRTM326 Wireless Router. 📉 **Version**: Versions **before 2.3.20**. If you have an older version, you are at risk!

Q: What can hackers do? (Privileges/Data)

💀 **Attacker Capabilities**: ✅ **Privileges**: Full system command execution. 📂 **Data**: High impact on Confidentiality, Integrity, and Availability (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Q: Is exploitation threshold high? (Auth/Config)

🔓 **Exploitation Threshold**: **LOW**. 🌐 **Network**: Remote (AV:N). 🔑 **Auth**: None required (PR:N). 👀 **User Interaction**: None (UI:N). ⚡ **Complexity**: Low (AC:L). Easy to exploit!

Q: Is there a public Exp? (PoC/Wild Exploitation)

📜 **Public Exploit**: **No** public PoC or wild exploitation detected in the provided data. ⚠️ **Note**: Lack of PoC doesn't mean it's safe; the CVSS score indicates high severity.

Q: How to self-check? (Features/Scanning)

🔍 **Self-Check**: 1. Check router firmware version. 2. Is it **< 2.3.20**? 3. Scan for SECOM WRTM326 devices on your network. 4. Look for unpatched instances in your infrastructure.

Q: Is it fixed officially? (Patch/Mitigation)

🩹 **Fix Status**: Yes, a fix exists. ✅ **Action**: Upgrade to version **2.3.20 or later**. 📚 **Reference**: Check TW-CERT advisory for official guidance.

Q: Is it urgent? (Priority Suggestion)

🚨 **Urgency**: **HIGH**. 📈 **Priority**: Critical. 📉 **Risk**: Remote, unauthenticated, high impact. Patch immediately to prevent total device takeover!

Updated May 08, 2026 CVSS 9.8 · Critical

This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis →

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: OS Command Injection in SECOM WRTM326 Router. <br>🔥 **Consequences**: Attackers can execute **arbitrary system commands** remotely. Total compromise of the device is possible.

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **CWE-78** (OS Command Injection). <br>❌ **Flaw**: Specific parameters are **not properly validated**. Malicious input bypasses checks and runs as system commands.

Q3Who is affected? (Versions/Components)

📦 **Affected**: SECOM WRTM326 Wireless Router. <br>📉 **Version**: Versions **before 2.3.20**. If you have an older version, you are at risk!

Q4What can hackers do? (Privileges/Data)

💀 **Attacker Capabilities**: <br>✅ **Privileges**: Full system command execution. <br>📂 **Data**: High impact on Confidentiality, Integrity, and Availability (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Q5Is exploitation threshold high? (Auth/Config)

🔓 **Exploitation Threshold**: **LOW**. <br>🌐 **Network**: Remote (AV:N). <br>🔑 **Auth**: None required (PR:N). <br>👀 **User Interaction**: None (UI:N). <br>⚡ **Complexity**: Low (AC:L). Easy to exploit!

Q6Is there a public Exp? (PoC/Wild Exploitation)

📜 **Public Exploit**: **No** public PoC or wild exploitation detected in the provided data. <br>⚠️ **Note**: Lack of PoC doesn't mean it's safe; the CVSS score indicates high severity.

Q7How to self-check? (Features/Scanning)

🔍 **Self-Check**: <br>1. Check router firmware version. <br>2. Is it **< 2.3.20**? <br>3. Scan for SECOM WRTM326 devices on your network. <br>4. Look for unpatched instances in your infrastructure.

Q8Is it fixed officially? (Patch/Mitigation)

🩹 **Fix Status**: Yes, a fix exists. <br>✅ **Action**: Upgrade to version **2.3.20 or later**. <br>📚 **Reference**: Check TW-CERT advisory for official guidance.

Q9What if no patch? (Workaround)

🚧 **No Patch? Workaround**: <br>🚫 **Block Access**: Restrict network access to the router's management interface.…

Read full answer (login)

Q10Is it urgent? (Priority Suggestion)

🚨 **Urgency**: **HIGH**. <br>📈 **Priority**: Critical. <br>📉 **Risk**: Remote, unauthenticated, high impact. Patch immediately to prevent total device takeover!

Continue exploring

Vulnerability detail Full AI analysis (login) SECOM CWE-78