CVE-2026-4164 — AI Deep Analysis Summary

Q: Who is affected? (Versions/Components)

📦 **Affected Product**: Wavlink WL-WN578W2 Wireless Repeater. 📅 **Specific Version**: Firmware V221110. ⚠️ **Vendor**: Wavlink (China Ruiyin).

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

👑 **Privileges**: Root/System level access. 📂 **Data**: Full read/write access to device files, network configuration, and potentially connected client data. 🌐 **Impact**: High (C) / High (I) / High (A) per CVSS 3.1.

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

🔓 **Threshold**: LOW. 🚫 **Auth**: No authentication required (PR:N). 🌍 **Access**: Network accessible (AV:N). 🖱️ **UI**: No user interaction needed (UI:N). This is a remote, unauthenticated attack vector.

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

📜 **Public Exp**: Yes. 📂 **Source**: GitHub repository `Litengzheng/vul_db` contains proof-of-concept code. 📢 **Advisories**: Multiple third-party submissions on VulDB confirm active exploitation potential.

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: CRITICAL. 🚨 **Priority**: Immediate action required. With CVSS 9.8 (implied by H/H/H) and no auth needed, this is a high-risk, easy-to-exploit vulnerability. Patch or isolate immediately.

Updated May 06, 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**: Critical Command Injection in Wavlink WL-WN578W2. 💥 **Consequences**: Full device compromise.…

Read full answer (login)

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: CWE-77 (Command Injection). 🐛 **Flaw**: Improper parameter handling in `/cgi-bin/wireless.cgi`.…

Read full answer (login)

Q3Who is affected? (Versions/Components)

📦 **Affected Product**: Wavlink WL-WN578W2 Wireless Repeater. 📅 **Specific Version**: Firmware V221110. ⚠️ **Vendor**: Wavlink (China Ruiyin).

Q4What can hackers do? (Privileges/Data)

👑 **Privileges**: Root/System level access. 📂 **Data**: Full read/write access to device files, network configuration, and potentially connected client data. 🌐 **Impact**: High (C) / High (I) / High (A) per CVSS 3.1.

Q5Is exploitation threshold high? (Auth/Config)

🔓 **Threshold**: LOW. 🚫 **Auth**: No authentication required (PR:N). 🌍 **Access**: Network accessible (AV:N). 🖱️ **UI**: No user interaction needed (UI:N). This is a remote, unauthenticated attack vector.

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

📜 **Public Exp**: Yes. 📂 **Source**: GitHub repository `Litengzheng/vul_db` contains proof-of-concept code. 📢 **Advisories**: Multiple third-party submissions on VulDB confirm active exploitation potential.

Q7How to self-check? (Features/Scanning)

🔍 **Self-Check**: Scan for open HTTP ports on Wavlink devices. 📡 **Target**: Send crafted POST requests to `/cgi-bin/wireless.cgi` with malicious payloads in `GuestWifi` or `SetName` parameters.…

Read full answer (login)

Q8Is it fixed officially? (Patch/Mitigation)

🛠️ **Official Patch**: Not explicitly listed in the provided data. 📝 **Status**: Vulnerability published March 2026. ⚠️ **Note**: Check vendor website for firmware updates > V221110.…

Read full answer (login)

Q9What if no patch? (Workaround)

🚧 **Workaround**: Block external access to the device's web management interface (port 80/443). 🛑 **Restrict**: Disable remote management features.…

Read full answer (login)

Q10Is it urgent? (Priority Suggestion)

🔥 **Urgency**: CRITICAL. 🚨 **Priority**: Immediate action required. With CVSS 9.8 (implied by H/H/H) and no auth needed, this is a high-risk, easy-to-exploit vulnerability. Patch or isolate immediately.

Continue exploring

Vulnerability detail Full AI analysis (login) Wavlink CWE-77