Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2024-43918 — AI Deep Analysis Summary

CVSS 10.0 · Critical

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: SQL Injection (SQLi) in WBW Product Table PRO. <br>💥 **Consequences**: Attackers can steal sensitive data, gain elevated access, or even achieve Remote Code Execution (RCE).…

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: CWE-89 (SQL Injection). <br>🔍 **Flaw**: Missing capability check on a function + improper neutralization of special elements. The plugin fails to validate inputs before executing SQL queries.

Q3Who is affected? (Versions/Components)

📦 **Affected**: WordPress Plugin: **WBW Product Table PRO**. <br>📅 **Versions**: 1.9.4 and earlier. <br>🏢 **Vendor**: WBW. If you use this plugin, you are in the danger zone.

Q4What can hackers do? (Privileges/Data)

💀 **Attacker Capabilities**: <br>1️⃣ Execute arbitrary SQL queries. <br>2️⃣ Steal sensitive database data (users, credentials). <br>3️⃣ Gain elevated access to the site.…

Q5Is exploitation threshold high? (Auth/Config)

⚡ **Threshold**: **LOW**. <br>🔓 **Auth**: **Unauthenticated**. No login required. <br>⚙️ **Config**: Low complexity (AC:L). Anyone on the internet can exploit this if the plugin is installed.

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

🔓 **Public Exploit**: **YES**. <br>📂 **PoC**: Available on GitHub (KTN1990/CVE-2024-43918). <br>🌍 **Status**: Wild exploitation is likely imminent since the proof-of-concept is public.

Q7How to self-check? (Features/Scanning)

🔍 **Self-Check**: <br>1️⃣ Scan your WordPress site for **WBW Product Table PRO**. <br>2️⃣ Check version number (≤ 1.9.4). <br>3️⃣ Use vulnerability scanners to detect SQLi endpoints in the plugin's API calls.

Q8Is it fixed officially? (Patch/Mitigation)

🩹 **Fix**: Update to the latest version immediately. <br>📢 **Official Patch**: The vendor (WBW) has released a fix. Check the WordPress plugin repository for the updated version.…

Q9What if no patch? (Workaround)

🚧 **No Patch?**: <br>1️⃣ **Disable/Deactivate** the plugin immediately. <br>2️⃣ **Delete** it if not needed. <br>3️⃣ Implement WAF rules to block SQL injection patterns targeting the plugin's endpoints.

Q10Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **CRITICAL**. <br>⏱️ **Priority**: **IMMEDIATE ACTION**. <br>📉 **Risk**: High CVSS score (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H). Unauthenticated + RCE potential = Do not wait.