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**: SQL Injection in Dokan Pro. π₯ **Consequences**: Attackers can manipulate database queries, leading to data theft, modification, or destruction. Critical integrity loss.
Q2Root Cause? (CWE/Flaw)
π‘οΈ **CWE-89**: SQL Injection. π **Root Cause**: Insufficient escaping of user-supplied parameters + lack of prepared statements in SQL queries. Specifically in `handle_moip_webhook`.
Q3Who is affected? (Versions/Components)
π¦ **Vendor**: wedevs. π¦ **Product**: Dokan Pro (WordPress Plugin). π **Affected**: Versions **3.10.3 and earlier**. π **Platform**: WordPress sites using this plugin.
Q4What can hackers do? (Privileges/Data)
π΅οΈ **Privileges**: Unauthenticated access required. ποΈ **Data**: Full read/write access to database. π **Impact**: High (CVSS Score indicates Complete Confidentiality, Integrity, and Availability impact).
Q5Is exploitation threshold high? (Auth/Config)
π **Threshold**: LOW. πͺ **Auth**: Unauthenticated (No login needed). βοΈ **Config**: Exploitable via specific webhook endpoint. π **Ease**: High risk due to low barrier to entry.
Q6Is there a public Exp? (PoC/Wild Exploitation)
π **Public Exp?**: YES. π **PoC**: Available on GitHub (truonghuuphuc/CVE-2024-3922-Poc). π§ͺ **Scanner**: Nuclei templates exist. β οΈ **Status**: Actively exploitable in the wild.
Q7How to self-check? (Features/Scanning)
π **Check**: Scan for Dokan Pro version <= 3.10.3. π‘ **Target**: Look for `/wp-content/plugins/dokan-pro/modules/moip/module.php` webhook calls. π οΈ **Tool**: Use Nuclei or manual PoC scripts to test the `code` parameter.
Q8Is it fixed officially? (Patch/Mitigation)
π οΈ **Fix**: Update Dokan Pro to version **> 3.10.3**. π **Source**: Check vendor changelog (dokan.co) for patch notes. β **Action**: Immediate upgrade recommended.
Q9What if no patch? (Workaround)
π§ **Workaround**: If unpatched, disable the Moip payment module or restrict webhook access via WAF. π« **Block**: Filter malicious SQL patterns in the `code` parameter at the network edge.
Q10Is it urgent? (Priority Suggestion)
π₯ **Urgency**: CRITICAL. π¨ **Priority**: P1. β³ **Reason**: Unauthenticated, high impact, public PoC exists. π **Action**: Patch immediately to prevent data breach.