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.